set_tempo

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Set the tempo' without mentioning side effects, constraints (e.g., Ableton tempo range), or whether changes apply immediately to live playback. This leaves significant behavioral ambiguity for a mutating operation.

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, consisting of one sentence plus a parameter listing. Every word earns its place, with no redundant information. This is a model of minimalism.

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 with a single parameter, the description covers the core meaning and parameter, but it lacks behavioral context such as side effects, error conditions, or return behavior. The absence of annotations and output schema means the description alone is not fully complete, though it is serviceable for basic invocation.

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 supplies the crucial semantic that the tempo is 'in BPM', which is absent from the schema (which only provides type and title). This adds real value beyond the structured data. However, it does not specify allowed ranges or default values, which would be even more helpful, but for a single parameter this is adequate.

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 explicitly states 'Set the tempo of the Ableton session', which is a specific verb + resource. It clearly distinguishes from sibling tools (e.g., set_track_volume, start_playback) as none of them handle tempo manipulation.

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 explicit when-to-use or alternative guidance is provided. The usage context is implied by the tool name and description, but the description does not state any exclusions or mention when to prefer this tool over others. Since no tempo-related sibling exists, the ambiguity is low, but clear guidance is still missing.

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