That is a very strong requirement and just because of space problems, I don’t think this can happen.
You could force a Message via code to components… Of course not suitable for components that already provide one… Once added you can remove the connection.
I work in icon mode and NEVER rename any input/output. What I do is add parameters when an important object/step is reached and rename that. But I see on your screenshot above you already do that. Yes, this is tedious to do on large definitions, but for me it’s the easiest to read.
There is MetaHopper’s Best Practicizer that can help for this thing.
Because most of GH native components do elementary things, I don’t find it useful to comment what they do, but rather what piece of the project comes out of them. It is however useful to label groups of components that together achieve a specific thing. I use GroupDisplay for the name to be visible when zoomed out, but Sunglasses (which I just added because I find it awesome even I don’t have the use of it) also has this option.
MessageComponent.gh (6.6 KB)