set_tempo

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

The description only repeats the tool's name and parameter, adding no behavioral details beyond what the name implies. The annotations provide destructiveHint: false, but the description does not elaborate on side effects, reversibility, or potential impacts on playback or automation.

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 and a parameter list. Every element earns its place, and the parameter is clearly labeled with its purpose.

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 setter tool, the description is minimally adequate. However, it lacks information about the expected range of BPM, whether it affects all tracks, or the return value. The presence of an output schema (not shown) may compensate, but the description itself is sparse.

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?

With 0% schema description coverage, the description adds crucial context by specifying that the 'tempo' parameter expects a value in BPM (beats per minute). This clarifies the unit, which is not evident from the schema alone.

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') and the resource ('tempo of the Ableton session'). It distinguishes this tool from siblings like set_track_volume or set_metronome by specifically targeting 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 context for its typical use. The agent receives no hints about prerequisites or situations where this tool is appropriate.

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