get_track_input_routing

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral transparency. It only states that it gets the input routing, but does not disclose what the return value looks like, whether it can fail, or any side effects (though likely none). This is a minimal disclosure that fails to provide meaningful behavioral context beyond the tool's name and basic action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise: two sentences with zero fluff. The first sentence states the purpose, and the second lists the parameter. This is appropriately sized for a simple getter tool and is front-loaded with the key action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is minimal and does not cover several important contextual aspects. There is no output schema, so the description should at least hint at the return value or format, but it does not. It also lacks guidance on usage, error conditions, or relationships to other routing tools. While the tool is simple, the description omits too much for a fully self-contained definition.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has one required integer parameter (track_index) with no description. The description adds 'The index of the track,' which provides a basic explanation but leaves ambiguity about indexing base (0 vs. 1), which track types are valid, or whether the index refers to session tracks, return tracks, etc. It helps but is not fully compensating for the 0% schema description coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action: 'Get the input routing of a track.' The verb 'Get' combined with the resource 'track input routing' is specific and unambiguous. It also implicitly distinguishes from sibling tools like set_track_input_routing and get_track_output_routing by its focus on reading the input routing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no explicit guidance on when to use this tool versus alternatives. While sibling tools like 'set_track_input_routing' suggest a read vs. write distinction, the description itself does not mention any usage context, prerequisites, or exclusions. There is no guidance on when to prefer this getter over other routing-related getters.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.