set_tempo

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

With no annotations, the description carries full responsibility but only states the action and unit. It does not disclose valid tempo range, side effects on playback, or prerequisites, leaving the agent to infer the operation's impact.

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?

A single short sentence with no redundancy, fully front-loaded with the verb 'Set' and the target resource.

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 core action is clear, but the lack of behavioral details or usage context makes it minimally viable. The presence of an output schema reduces the need to describe return values, but no mention of constraints or related tools limits completeness.

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?

Schema coverage is 0%, but the description clarifies that the 'tempo' parameter is in BPM. However, it adds no details on range, precision, or validation, so it only partially compensates for the bare schema.

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 uses a specific verb 'Set' and a clear resource 'session tempo' with the unit 'BPM'. It unambiguously distinguishes from sibling transport tools like set_song_position or set_time_signature.

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 when-to-use, exclusions, or alternative guidance is provided. The description simply states the action without any context on when it should be used relative to other transport-related tools.

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