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

The readOnlyHint and openWorldHint annotations already establish this as a safe, local, side-effect-free computation, so the description only needs to add output-behavior detail. It does add that results are broken out as straight/dotted/triplet note lengths, but it says nothing about which note values are returned or how the result is structured.

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 that front-loads the core transformation and appends the practical use cases; there is no filler and nothing redundant.

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, side-effect-free converter with readOnly annotations, the description covers the input domain, the nature of the output, and typical uses. The only gap is that the return shape (e.g., keys per note value) is unspecified and there is no output schema to fall back on.

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 0% for the single bpm parameter, so the description is the only source of parameter meaning. It indirectly identifies bpm as 'a tempo' but offers no unit clarification (BPM vs Hz) and never mentions the schema's 20-400 range, so it only partially compensates for the coverage gap.

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 precise transformation: tempo -> note lengths in milliseconds, with the three subdivision types named (straight, dotted, triplet). No sibling tool (capo_finder, chord_info, scale_info, transpose_chords) does timing conversion, so the agent can identify this tool's unique job immediately.

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?

It gives concrete application contexts (setting delay, reverb pre-delay, LFO times), which tells the agent when this tool is the right pick. It stops short of any when-not-to-use or alternative-tool routing, but no plausible alternative exists among the siblings.

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