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

Annotations declare a non-read-only, non-idempotent, open-world operation, and the description goes further by disclosing the verification behavior and the exact result signals (confidence level, share of notes kept, lost features, repaired exporter quirks). That is meaningful context beyond the annotations, though it never states whether a file is created/persisted server-side or any cost/latency implications of open-world fetches.

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?

Front-loaded with the core action, split into a purpose line and a result line, with zero filler sentences. Slightly dense phrasing ('exporter quirks that were repaired on the way in') but nothing that should be cut.

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?

An output schema exists, so return values need not be re-explained, and the description already frames the verification semantics well. The gap is input-path ambiguity: for a tool where the score can arrive by URL, by upload link, or inline text, the description never says which of `file`/`content` is needed, which is the main thing an agent could get wrong.

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 100%, so the schema already explains `to`, `file`, `content`, and `filename`; the description only loosely restates the target-format set. It adds no help on the important choice between `file` and `content` (mutually alternative input paths) or how `filename` interacts with `content`, so it does not exceed the baseline.

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 gives a specific verb+resource ('Convert a score between formats') and enumerates the two output modes (notation formats vs. sheet music/audio), which makes the tool's function immediately graspable. It stops short of distinguishing itself from the overlapping sibling `render` (which plausibly also produces pdf/png/svg/wav), so the agent must infer the boundary.

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 by describing what the conversion does plus the note-by-note verification, but there is no explicit when-to-use vs. when-not guidance. With siblings like `render`, `validate`, and `compare` present, an agent gets no rule for choosing `convert` over those; the verification clause in particular muddies the line with `validate`.

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