get_input_audio_tracks

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

No annotations are provided, so the description carries the burden. It adds the useful detail that there are exactly 6 audio mixer tracks, but it does not disclose the return format, potential errors, or behavior in edge cases. For a simple read operation, this is minimally acceptable.

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 a single, front-loaded sentence that clearly communicates the tool's function without any filler or redundancy. Every word contributes to understanding.

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?

For a simple one-parameter getter with no output schema, the description conveys the primary purpose but omits details about the return value (e.g., whether it returns booleans, track numbers, or a list). This leaves some ambiguity about what the agent will receive.

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 provides no description for the input_name parameter (0% coverage), and the description does not explain it beyond referencing 'this input'. While the parameter name is self-explanatory, the description adds no additional context about expected values or format.

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 intended operation: retrieving which of the 6 audio mixer tracks a given input is routed to. It uses a specific verb ('get'), identifies the resource ('audio mixer tracks'), and includes scope ('6'), distinguishing it from sibling tools like get_input_volume or get_input_balance.

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?

There is no guidance on when to use this tool versus alternatives or exclusions. The description simply states the functionality without context on when it would be appropriate, such as comparing to set_input_audio_tracks or other audio-related getters.

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