It ultimately depends on why you want the labels.
For me the most important thing is so that when something needs plugging back in, you don't have to trace the cables with your fingers - impossible in some circumstances. Your scheme would facilitate that, although you probably want to include:
- Device/Patch ID (could be a server, switch, other network device or
just a patch panel)
- Interface ID (specifically which port the cable
should be plugged into)
Include details of both ends of the cable at both ends, since sometimes you want to know where the far end of the cable goes!
I would say it is useful to use the physical labelling on the devices themselves, and then keep documentation of how that maps through in the specific system (e.g. NIC on a server may be labelled A, but in the OS it is eth0). Where you have multiple interface cards with multiple ports, you should agree and document a naming convention.
If you use VLANs you might want to include VLAN ID, or you might want to use different colour cables for different things.
I would avoid any tags that snag, and definitely anything that falls off easily.