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 fully covered. The description adds only that output is MusicXML for a subset of parts; it says nothing about the save_to write path (schema notes stdio-only) or that extraction requires a completed recognition.

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?

Two short sentences with zero filler, and the core resource (part MusicXML from a recognised score) is front-loaded. The opening noun fragment is slightly clipped but effective.

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 an output schema, full parameter descriptions and complete annotations, most burden is lifted; the description only needs to convey scope and the part-name lookup path, which it does. The remaining gap is the relationship to get_musicxml/export_score, which an agent may need to disambiguate sibling choice.

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%, including the accepted part id/name/number formats and multi-part comma syntax, so the schema carries the burden. The description contributes the extra fact that valid part names come from describe_score, which slightly helps the `part` parameter but is not format detail beyond 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?

States a specific verb+resource: returns the MusicXML of one or a few parts of a recognised score, with a concrete example (alto line of a choir piece). It does not explicitly distinguish itself from get_musicxml or export_score, so the agent must infer that this is the partial-extraction counterpart.

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?

Provides one concrete workflow hint — 'Part names are in describe_score' — which tells the agent how to obtain a valid `part` value. However, it never states when to choose this over get_musicxml/export_score or what happens if the score isn't recognised yet.

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