One possible counter-argument to this recommendation concerns using the SysML Requirements system:
Verbose block property names and port names can help tracing participation of properties and ports in requirements relationships and play nicely with current SysML callout style.Alternatively, if you must name a Port (because you need to for queries, for example):
Webel Best Practice: UML/SysML: In Internal Block Diagrams: Consider hiding the name of a named Port or Property in a Diagram if its Type is sufficient to indicate its role.
Webel Best Practice: If you must name your Ports or Pins, name them simply 'i', 'o', or 'io' to indicate direction UNLESS you have to indicate a special role like 'iRole', 'oAuxiliary'. DO NOT use Port names like 'input', 'output', etc.