Compare two tempos

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

With no annotations, the description carries the full burden. It usefully discloses that the comparison accounts for half-time and double-time interpretations, which is real behavioral context beyond the name. But it never says whether this is a pure read-only computation, whether it returns a boolean match, a ratio, or a ranked set of interpretations, or what tolerance counts as 'equal'.

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 sentence with no filler, and the most discriminating information (half-time/double-time handling) is front-loaded. It is efficient, though its brevity is partly the source of the gaps elsewhere rather than a pure virtue.

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?

The tool is simple (two numeric inputs, no output schema), but for a comparison tool the shape of the result is the whole point, and the description says nothing about it. An agent knows what goes in and roughly what the tool reasons about, but not what comes back.

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%, so the description must compensate. It only mentions 'reported BPMs' in passing; it does not state that the two parameters are the two numeric BPM values being compared, nor anything about the valid 0-500 range or whether order matters. The self-explanatory parameter names (firstBpm, secondBpm) rescue this to a minimum-viable 3.

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?

Specific verb (compare) plus specific resource (reported BPMs), and it adds a meaningful qualifier: half-time and double-time interpretations. That qualifier distinguishes it from a plain numeric comparison and plausibly from the sibling tempo_timing, though the description never names the sibling to make the contrast explicit.

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 phrase 'reported BPMs' implies the scenario (reconciling two conflicting tempo readings), but there is no explicit when-to-use, no when-not-to-use, and no reference to tempo_timing as the alternative for single-tempo analysis. Usage is inferable rather than stated.

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