transpose_by_key

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

No annotations are provided, so the description carries the full burden. It discloses the dependency on MuseScore CLI, the direction default, and the return value (Base64-encoded mscz). It does not mention permissions or side effects, but the tool appears non-destructive as it returns a new file.

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 structured with Args and Returns sections, making it easy to parse. It is detailed without being verbose, though the key list could be abbreviated. Every sentence serves a purpose.

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 tool has 4 parameters, no annotations, and an output schema exists, the description covers the core functionality, prerequisites, and return format. It lacks error handling details or non-happy-path behavior, but it is complete enough 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 coverage is 0%, but the description adds meaning to all parameters: explains target_key with a list of major keys, direction with allowed values and default, and input_suffix with an example. score_b64 is mentioned but could benefit from format constraints. Overall, it compensates well for the lack of schema descriptions.

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 'Transpose a score to a target key using the MuseScore CLI,' providing a specific verb and resource. It lists target key options and direction, distinguishing it from siblings like transpose_by_interval and transpose_for_instrument.

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 mentions the prerequisite 'Requires MuseScore 3.3+ with --score-transpose support,' but does not provide guidance on when to use this tool versus sibling transpose tools. Implied usage is clear but no explicit exclusions or comparisons.

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