transpose_notes

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

Annotations already set destructiveHint=true, indicating mutation. The description clarifies the resource ('take's notes') and purpose ('key/mode retargeting'), but doesn't disclose additional behavioral details such as exactly which properties are modified or any prerequisites.

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 single-sentence description is concise and front-loaded with key action and resource. However, it could include brief parameter hints without becoming verbose while still adding 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?

Despite having an output schema and only two parameters, the description omits critical context: what happens to existing notes, whether the transpose is absolute or relative, and any constraints on semitones. This is insufficient for a mutation tool with destructiveHint=true.

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% with no parameter descriptions. The description does not explain the 'track' or 'semitones' parameters, forcing the agent to rely solely on names. This is a significant gap for a tool with only two required parameters.

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?

Specific verb 'Transpose' and resource 'take's notes' clearly stated. The phrase 'APPLY verb for key/mode retargeting' distinguishes it from sibling tools like 'constrain_to_key' which may set a fixed key rather than transpose.

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 after key/mode retargeting analysis but lacks explicit when-to-use or when-not-to-use guidance. No alternatives are listed, leaving the agent to infer context from the sibling list.

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