Without the @Override coded above the toString() method, would the constructor be called instead?

The toString and the class Constructor are two different things. The constructor instantiates or sets up the data for new objects that you create. These can be hard-coded or passed as arguments to the constructor. For example, if you created a car class and created a new instance of that car, you're constructor may start the car off having 4 tires, 1 windshield, 2 wipers, etc. What you would expect to be in a standard car. The toString method is inherited from the Object class. All classes even your custom classes inherit the based methods of the Object class (toString is one of these methods).

The @Override annotation lets other developers and the compiler know that you're overriding the inherited default toString method with something that more aptly meets your needs. @Override isn't necessary and simply lets the compiler know what your intention is.

As best practice, I would always stress using proper annotation so that you can take advantage of the compiler checking to make sure you actually are overriding a method when you think you are. This way, if you make a common mistake of misspelling a method name or not correctly matching the parameters, you will be warned that you method does not actually override as you think it does. Secondly, it makes your code easier to understand because it is more obvious when methods are overwritten.

I hope this helps :)