set_tempo

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

With no annotations provided, the description must disclose behaviors like side effects, range limits, or session requirements. It merely restates the action ('Set the tempo') without any further detail, which is essentially a tautology and fails to inform the agent of anything beyond the name.

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 exceptionally concise: a single sentence identifying the action followed by a two-line parameter list. There is no redundant or vague wording—every sentence adds direct value.

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, the description covers the essential facts (what is changed and how the parameters map). However, it omits any mention of return values, validation ranges, or whether the session must be running, leaving some gaps in the absence of an output schema.

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 explains both parameters: 'tempo' is explicitly in BPM, and 'user_prompt' is identified as telemetry. This adds meaningful context that is absent from the input schema (which only provides types and defaults), compensating well for the 0% schema description coverage.

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 verb 'Set' and the resource 'tempo of the Ableton session', making its function unambiguous. It naturally distinguishes from sibling tools since no other tool in the list deals with tempo setting.

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 gives no guidance on when to use this tool versus alternatives, no prerequisites, and no context about how it fits into a workflow. It simply states the action without explaining when it is appropriate.

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