Convert BPM to timing

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It says audio is not accessed, which is useful, but it does not clarify whether the tool is a pure calculation, whether it has side effects, what permissions are needed, or whether the output is deterministic.

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 two short sentences and is front-loaded with the action and output quantities. Every clause adds information, including the explicit note that audio is not accessed, 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?

For a simple two-parameter calculator with no output schema, the description names the return quantities but omits their units or formatting and does not explain the second parameter. It is adequate but leaves meaningful gaps for an agent trying to predict exact input semantics.

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 by explaining the parameters. It only implies that 'bpm' is the input and says nothing about 'beatsPerBar', its default value, or how it affects the computed bar length.

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 verb and resource: it converts BPM into beat, subdivision, and bar lengths. It does not explicitly distinguish itself from the listed siblings, but the output domain is clearly different from compare_tempos, camelot_neighbors, and get_official_links.

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 'known BPM' implies the tool should be used when the tempo is already established, and 'Audio is not accessed' rules out audio analysis. However, it names no alternative tool and gives no explicit when-not guidance, so the usage context remains implied rather than stated.

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