set_tempo

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the valid BPM range but says nothing about side effects, required permissions, whether changes are reversible, or how playback is affected. For a mutation tool, this is a significant gap.

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 a single, front-loaded sentence that contains the core action and the key constraint. Every element earns its place, and there is no redundant text.

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 one-parameter setter with no output schema, the description covers the essential action and range. But with no annotations and no return-value explanation, an agent lacks context about success/failure behavior or whether the tempo change applies immediately.

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 coverage is 0%, so the schema only says 'bpm' is a number. The description compensates somewhat by specifying the unit (BPM) and valid range (10..522). However, it does not clarify whether fractional values are accepted, what the default is, or what happens on out-of-range input.

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 ('Set the tempo') with the valid BPM range, making the tool's function immediately clear. It does not explicitly differentiate from siblings such as set_time_signature or set_project_settings, but the tempo focus is unambiguous.

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?

Usage is implied by the tool name and description—an agent can infer this is for changing project tempo. However, there is no explicit guidance about when to prefer this over alternatives like set_project_settings or any preconditions (e.g., playback state).

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