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

Annotations already cover read-only, non-destructive, closed-world behavior. The description adds substantial operational detail: returned artifacts, ascending/descending support, 20-400 BPM range, up to 200 stages, percent-step rounding, target-stage timing, and explicit non-capabilities.

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?

The description is compact and front-loaded with the usage trigger. Each sentence carries useful information: the use case, the outputs, the operational limits, and the exclusions.

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 detail return fields, and it already summarizes key outputs. Given the annotations and full schema coverage, it provides enough context for an agent to select and invoke the tool correctly.

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%, so the schema already documents all five parameters. The description adds a few useful hints, such as ascending/descending and the 200-stage cap, but it does not meaningfully enrich the per-parameter semantics beyond what the schema provides.

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 specific use case: building a tempo ladder from start to target BPM with step and minutes per stage, and returning a ladder table, total time, and CSV. It is clear what the tool does, but it does not explicitly name or contrast with the sibling tools calculate_tempo_values or show_metronome.

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 a clear trigger: 'Use this when the user wants a metronome for practice with a tempo ladder...'. It also notes what the tool does not do (track sessions or record audio), but it does not explicitly say when to prefer a sibling tool such as show_metronome or calculate_tempo_values.

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