I'm a user who doesn't much care about link following command behavior, but Bastien's point about context is important. The behavior of a command needs to depend upon much more than just syntax.
Two really dramatic examples are region narrowing and outline folding. When operating on a narrowed region there are a great many differences in how commands behave. Similarly, when a headline is folded, commands behave very differently. So be very careful to include consideration of the context when defining commands. Some context is much more subtle. My one link related comment is that I'm very puzzled by those who think that links in comments should not be followed. In programs I make heavy use of links in comments so that the comment can include a "see this [document]" as part of the comment. It's a link that other programmers want to follow. I don't often put comments into my org files, but I would expect to follow links in them also. In programming a comment means "don't try to compile or execute this". It doesn't mean destruction of all other semantic value. It means a highly selective removal of semantics. I would expect links in comments to still be followable. R Horn