transpose

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

With no annotations provided, the description carries the full burden. It discloses that the operation is selection-only, notes the precedence of octave over chromatic, and maps to internal NoteEdit commands. It doesn't discuss permissions or reversibility, but for a simple transpose operation this is reasonable.

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 front-loaded with the main purpose, followed by a clear Args section and behavioral note. It is a bit longer than necessary due to the internal mapping mention, but every sentence provides useful information without redundancy.

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?

The description covers purpose, parameters, selection requirement, and parameter precedence. It doesn't explain return values, but an output schema exists, and the tool is simple enough that this is not a critical omission.

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 has 0% description coverage, but the description compensates fully by explaining each parameter: direction ('up' or 'down'), chromatic (chromatic semitone), and octave (whole octave, with precedence). This adds significant meaning beyond the bare schema.

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 transposes the current selection up or down, using a specific verb and resource. It distinguishes itself from sibling tools like add_notes or set_key_signature, which handle different operations.

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 provides clear context by stating it operates on whatever is selected in Dorico and explicitly instructs to make a selection first. It doesn't mention when not to use it or alternatives, but the selection requirement gives adequate usage guidance.

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