set_tempo

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

No annotations are provided, so the description must disclose side effects, constraints, or reversibility. It only states the action without mentioning the effect on the session state, acceptable tempo range, or whether the change persists. The telemetry note for user_prompt is helpful but does not cover the mutation's behavioral footprint.

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 two sentences, front-loads the core action, and then lists parameters compactly. No wasted words; the telemetry explanation is valuable and placed after the primary 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 mutation tool with no annotations and no disclosed output schema, the description is incomplete. It does not state whether the operation is reversible, what happens if the tempo is out of range, or any confirmation message. The existence of an output schema is not reflected, so the agent cannot anticipate the response.

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 compensates by explaining both parameters: tempo is in BPM and user_prompt is for telemetry. This adds meaning beyond the raw schema types. However, it lacks detail on tempo valid range or formatting, so it is not a full 5.

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 'Set the tempo of the Ableton session' with a specific verb and resource. It is easily distinguished from sibling tools like set_track_name or set_device_parameter by the explicit resource and domain (Ableton 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?

The description gives no guidance on when to use this tool versus alternatives or context for its invocation. It does not mention conditions, prerequisites, or typical use cases beyond the bare action.

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