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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine content-level context by spelling out what each topic returns (complete genre templates, preset behavior, GM list plus combos, drum patterns plus percussion notes), which tells the agent what to expect from the call.

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 with the resource statement front-loaded and the topic inventory following as a compact list; every clause maps to a real capability. Slightly list-heavy, but there is no filler.

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?

For a one-parameter, read-only reference tool with no output schema, the description covers the topics well enough that the agent knows what each call yields. The only missing element is routing versus the sibling search and guide tools.

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% with a single enum parameter, so the schema already carries the parameter semantics and baseline is 3. The description largely restates the enum values, though it does add specificity for 'genres' (jazz, blues, folk, rock, bossa, minuet, lullaby) that is not in the 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 states a concrete resource ('Reference for ABC sheet music') and enumerates the seven content topics, so an agent knows exactly what kind of artifact this returns. However, it never differentiates itself from the closely named sibling search-music-docs or get-strudel-guide, leaving the agent to infer that this is a static reference rather than a search.

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?

Usage is only implied by the nature of a reference tool; the description gives no when-to-use framing and never names alternatives such as search-music-docs for free-text lookup or get-strudel-guide for the other notation language. The routing hint ('Start with genres...') lives in the schema's enum description, not in the tool description itself.

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