songsterr_transpose

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

Annotations provide idempotentHint=true, and the description adds that pitch is preserved, and returns ASCII tab or .gp5 path plus playability warnings. No contradictions. Describes outputs and warnings beyond annotations.

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?

Two sentences, front-loaded with key action, no redundant words. Every sentence adds value.

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?

Given well-documented schema and existing output schema, the description covers purpose, key behavior, and outputs. It lacks explicit mention of file prerequisites but the parameter schema covers that. Overall sufficient.

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?

Schema descriptions already document all parameters, so the tool description adds marginal value (e.g., 'preserving pitch'). The description's additional context about 'plus any playability warnings' is helpful but not critical.

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 tool re-fingers a track to a new tuning while preserving pitch, and mentions semitone_shift for key change. It distinguishes from siblings: songsterr_get_tab retrieves tabs, songsterr_list_tunings lists tunings, songsterr_search_songs searches.

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 implies usage for transposing tracks onto new tunings, but does not explicitly state when to use vs alternatives, nor when not to use. Prerequisites (file from songsterr_get_tab) are in the parameter schema, not description.

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