with tablevalued CLR functions, SQLcomplete shows both output and input variables in the tip, making it hard to use the correct input variables.

instead the tip should only show input variables when you are typing input variables and output variables when you are in the select part, right now both input and output variables are suggested regardless of where you are typing, making it next to useless in aiding with the SQL typing.
I submitted this as a bug, but got the reply that this was by design, but with no explanation as to why they think this is a useful behaviour, I cannot think of a situation where it helps to show both input and output mixed together in the intellisense, and if this is by design, then why are the plain SQL tablevalued functions not behaving like this???