transpose_for_instrument

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

With no annotations, the description carries full transparency burden. It discloses that the tool modifies the <transpose> element, returns modified MusicXML, and affects the specified part(s). However, it does not mention potential side effects, required permissions, or whether the operation is reversible.

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 well-structured with a concise intro, an example list, and an Args table. It avoids redundancy and is front-loaded with purpose. The list of known instruments is useful but could be shortened; overall efficient.

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 the 6 parameters, lack of schema descriptions, and no annotations, the description covers the core functionality, return type, and parameter interactions. It omits error handling, input validation, and performance constraints, but is adequate for typical use.

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 description coverage is 0%, so the description fully compensates by explaining each parameter in the Args section: score_b64, input_suffix, instrument shorthand, chromatic/diatonic offsets, and part_index with default behavior. It clarifies the mutual exclusivity of instrument vs explicit offsets.

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 it adjusts transposition offsets for transposing instrument parts via the MusicXML <transpose> element. It provides concrete examples (Bb clarinet, alto sax) and distinguishes from sibling tools like transpose_by_interval by offering instrument shorthand as an alternative to explicit intervals.

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 explains how to use the tool (pass instrument or chromatic+diatonic) and lists known instruments, but does not explicitly state when this tool should be preferred over transpose_by_interval or transpose_by_key, nor does it warn about non-transposing instruments or prerequisites.

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