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

Annotations already indicate a non-read-only, non-destructive, non-idempotent operation. The description adds meaningful behavior: an 80-character limit, empty-name clearing, label-only mutation, preservation of history, and a prompt-injection warning about names being user content. It does not mention what happens on stale expected_name, though the schema covers that.

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?

Three short sentences, front-loaded with the core effect and limits. Every sentence earns its place, including the final safety note about user content.

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 mutation tool with annotations and no output schema, the description covers the mutation's effect, constraints, and safety. Minor gaps remain around conflict behavior and how to obtain score_id/revision, but the essential calling context is present.

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 coverage is 50%, so the description partially compensates by explaining the name parameter's length limit and empty-clears behavior. It does not explain expected_name's concurrency-control role or score_id, but revision and expected_name already have schema descriptions.

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 and resource ('Name a saved version') and clarifies the scope: it changes only the label while music, current version, and history stay. This implicitly distinguishes it from edit/revise tools, though it does not name a sibling alternative explicitly.

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 implied: use this to assign or clear a version's name. It notes that an empty name clears the label, which is useful, but it does not say when to use this versus list_score_versions or restore_score_version, nor does it mention prerequisites such as needing the current name from the version list.

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