set_tempo

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states 'Set the tempo' without mentioning side effects, constraints (e.g., BPM range), or impact on playback. This is insufficient for a mutation tool.

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 short and front-loaded with the main action. The parameter listing is included but is redundant with the schema. It earns its place by adding the BPM unit.

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?

The tool is simple with one parameter, and the description provides the parameter's meaning and unit. However, it does not mention the return value or any potential errors, which is acceptable for a straightforward setter but not complete.

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 input schema has 0% description coverage, but the description adds the unit 'BPM' to the parameter, which provides essential meaning beyond the schema's title 'Tempo'. This compensates for the schema's lack of detail.

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 of the Ableton session.' It uses a specific verb ('set') and resource ('tempo of the session'), and is distinct from all sibling tools.

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 description implies the tool is used to set tempo but provides no explicit guidance on when to use it versus alternatives, or any prerequisites. There are no sibling tools that set tempo, so the lack of explicit guidelines is somewhat mitigated.

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