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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is covered. The description usefully adds that pitches are preserved and that the operation re-derives string/fret placement, but it never says existing fingering is overwritten in place, whether the change is undoable, or how it interacts with the draft/save flow.

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?

A single dense sentence, front-loaded with the operation's effect and then the mode/capo options. Nothing is padded, though the mode list compresses three definitions into parentheticals that could be hard to parse quickly.

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?

An output schema exists, so return values need not be explained, and annotations carry the safety profile. Still, for a destructive in-place mutation on a draft, the description omits prerequisites (how to obtain 'draft'), scope behavior (track defaults to every track) and reversibility, leaving real gaps.

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 100%, so all four parameters are already documented with defaults and enum values. The description largely restates mode and searchCapo wording that is identical to the schema, adding only the 'string and fret' framing; baseline 3 applies.

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 gives a concrete verb+resource: re-placing the notes of a draft onto the neck as string/fret while preserving pitches. That is far more specific than the vague title 'Place the notes again'. It stops short of naming the closest sibling (transpose) explicitly, so the agent must infer the contrast from 'keeping their pitches'.

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?

'Keeping their pitches' implicitly distinguishes this from transpose, which changes pitches, and the mode explanations hint at selection criteria. However there is no explicit when-to-use/when-not statement, no mention of prerequisites (a valid draft id from a previous tool), and no named alternative.

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