Yes, your proposal is more consistent with the existing methods. 

But I tried to follow this proposal: http://markmail.org/message/e7e6oxwhfa6wmvas :
> 1) Specify your own String from the UI OR
> 2) (optionally) Specify your own translation key from the UI OR
> 3) Fall back on a default translation key convention 
> 4) (optionally) Make up your own translation key convention 

I tried to make 1) and 3).

I didn't manage to add the ability to use velocity code in the hint, in order to use $services.localization for example.

Now, I would prefer to do it the way you say, because it is already how pretty names work. But I don't know if everybody agree.