set_tempo

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

No annotations exist, so the description carries the full burden of behavioral disclosure. It only states the action and parameter; it does not mention valid BPM ranges, whether setting tempo affects playback, or any side effects such as timeline changes. This is a mutation tool with no warning or contextual behavior.

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 remarkably concise: one action sentence plus a clear parameter listing. Every word earns its place, and there is no repetition of schema details beyond the essential unit clarification.

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 single-parameter setter with an output schema, the description is mostly complete. The only notable gap is the absence of a valid tempo range (e.g., Ableton's 20-999 BPM), which could lead an agent to attempt an invalid value. The role and unit are covered, and no nested complexity exists.

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%; the description compensates by explaining 'tempo: The new tempo in BPM', adding the unit (BPM) and semantic role ('new tempo') that the schema lacks. It does not specify an allowable range, but for a single parameter it adds meaningful meaning beyond the schema.

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 uses a specific verb ('Set') and resource ('the tempo of the Ableton session'), making the tool's single responsibility unmistakable. It also distinguishes itself from sibling tools like set_track_volume and set_track_name because none of them target tempo.

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?

No guidance is provided on when to use this tool versus alternatives, nor any exclusions or prerequisites. While the action is obvious from the name, the description does not offer context such as 'use this for global session tempo' or mention any relation to get_session_info.

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