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

Beyond the read-only and idempotent annotations, the description discloses input limits, supported formats, that controls invoke transpose_chords, what the output includes (original key, chord counts, Latin-only Courier PDF), and an important limitation about key estimates for modulating songs. These details materially improve behavioral understanding.

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 primary use case and then efficiently layers in input formats, output contents, exclusions, and limitations. Every sentence carries useful information without repetition.

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?

With annotations, a fully described input schema, and an output schema, the description supplies the remaining context an agent needs: format support, length limits, output characteristics, exclusions, and known key-estimation limitations. Nothing essential for correct invocation appears missing.

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 already have documented semantics. The description adds context about chord sheet length and formats, but it does not specifically clarify title, from_key/to_key behavior, or spelling beyond what the schema provides, so baseline 3 is appropriate.

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 a specific resource and behavior: a live chord sheet with -1/+1 semitone controls, accepting chord-line or ChordPro input. It also distinguishes the tool from transpose_chords by explaining that the controls call that sibling, so an agent can identify this as the presentation/PDF tool rather than the raw transposition tool.

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?

It gives a clear use condition: 'Use this when you want a live chord sheet with -1 and +1 semitone controls.' It also provides useful exclusions such as no audio, tablature, or staff notation, though it does not explicitly say when to choose find_capo_options instead.

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