set_tempo

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

Without annotations, the description carries full responsibility for behavioral disclosure. It only states that the tempo is set, but does not explain side effects (e.g., immediate change to playback, persistence, constraints like tempo range). This leaves significant gaps for an AI agent.

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 extremely concise: one sentence for purpose and a line for parameter details. Every word earns its place. No redundancy or fluff.

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?

Given the tool is simple with one parameter and no output schema, the description conveys the core function. However, it lacks constraints (valid tempo range) and does not acknowledge the existence of a similar tool ('set_scene_tempo'), which would improve completeness.

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?

The description adds the unit 'BPM' to the parameter 'tempo', which is not in the schema. This provides helpful semantics. However, no range, precision, or formatting details are given, and schema coverage is 0%. The added value is moderate.

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 clearly states the action ('Set the tempo') and the resource ('the Ableton session'). It provides a specific verb and resource, making the purpose immediately understandable. However, it does not differentiate from the sibling 'set_scene_tempo', which could cause confusion about whether this sets the global tempo or a scene-specific 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 like 'set_scene_tempo'. There is no mention of context, preconditions, or exclusions. The minimal description assumes the user already knows when to invoke it.

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