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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is fully covered and the description need not restate it. The description adds domain context that output is a delay time in milliseconds per note value, but says nothing extra about precision, rounding, or bounds beyond what the schema's min/max already imply.

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, both earning their place: the first states the transformation and its output unit, the second routes to related calculators. The core purpose is front-loaded with 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?

With an output schema present, the description need not explain return values, and both required parameters are fully documented in the schema, so the definition is sufficient to invoke the tool correctly. The remaining gap is the absence of explicit when-to-use/alternative guidance for a very narrow computation.

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% and the enum of note values is fully enumerated in the schema, so the structured fields already carry the parameter meaning. The description adds no syntax, range, or format detail beyond the schema, making the baseline 3 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 names a specific verb (Convert) and a precise resource (BPM tempo to millisecond delay times), with the note-value dimension called out, so an agent knows exactly what transformation this performs. It does not explicitly differentiate itself from adjacent music/time siblings such as calculate_frequency_note or calculate_reverb_predelay, which is the only thing keeping it from a 5.

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?

The only guidance is a navigation pointer ('See list_bundles for related musique calculators'), which tells the agent where related tools live but not when to choose this tool over alternatives. There is no statement of prerequisites, input ranges, or when-not-to-use, leaving the agent to infer usage from the purpose sentence alone.

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