No.
I could think of two reasons not to do that.
- In many models, many signal lines have no label (i.e. the "signal names" are empty or blank).
- I saw this problem happened quite a few times. In the model, there is a signal line with label (signal name) called "MySignal". It is resolved to a Simulink.Signal object called "MySignal" in the base workspace. If the tag of a Goto block is also set as "MySignal", then after a simulation, the saved signal logging "MySignal" would over-write the Simulink.Signal object "MySignal". There will be an error message for the next simulation.
There are measures available to avoid both. But considering these, I don't think "auto tagging signal name" is a good idea.
