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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description does not need to repeat safety traits. The description adds behavioral context by mentioning 'voice-leading score', indicating that previousNotes influences the output. However, it does not disclose any other behavioral traits such as authentication needs or rate limits.

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 a single sentence with no redundant words. It conveys the core purpose and a key parameter usage efficiently.

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 5 parameters and no output schema, the description is insufficient. It fails to explain multiple parameters (style, octave, keyContext) and the nature of the return value. The description leaves significant gaps for an agent to correctly invoke the tool.

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 must compensate. Only 'previousNotes' is explained (for voice-leading), leaving four other parameters (chord, style, octave, keyContext) completely undefined. The description adds little value beyond the parameter names.

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 states it generates an 'instrument-ready voicing in a style', clearly indicating the tool's function. It also mentions using previousNotes for voice-leading, which distinguishes it from siblings like analyze_chord or reharmonize. However, it could be more explicit that the output is a voicing (a set of notes) and not a chord symbol.

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?

No explicit guidance on when to use this tool versus its siblings (analyze_chord, reharmonize, resolve_chord). The only usage hint is 'pass previousNotes for a voice-leading score', which implies a conditional use but does not specify when not to use or what scenarios are appropriate.

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