Hi Alan,
This should really be posted in the TS Forum.
The TS API knows nothing of the LabVIEW API in itself, other than calling the VI through the step type adapter.
You could generate a sequence that contains a generic .vi that would look at a step and work out where the .vi was, and then get a handle to that .vi, and pull the information on the description etc from that .vi into the step's comment field, which is easy to display, so you'd run your "tool" sequence over the loaded sequence to populate all the appropriate steps -= does that make sense?
S.
// it takes almost no time to rate an answer