set_tempo_change

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

No annotations are provided, so the description carries the full burden. It describes the action as scheduling a tempo change but does not disclose behavioral traits such as whether multiple tempo changes can coexist, if the change is reversible, or if it has any destructive side effects.

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?

Two sentences with no wasted words. The first sentence defines the core function, and the second provides concrete, memorable examples. Perfectly concise.

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?

Given the tool has an output schema, the description need not explain return values. However, the description lacks detail on parameter semantics and behavioral traits, making it not fully complete for a tool with no annotations and zero schema documentation coverage.

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 description coverage is 0%, so the description must compensate. While it mentions 'at a specific absolute beat' (time_in_beats) and 'tempo change' (new_bpm), it does not explain the project_name parameter, and the descriptions are minimal. More detail is needed to fully clarify parameter meaning.

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?

Clearly states the tool schedules a tempo (BPM) change at a specific absolute beat. The verb 'Schedule' and resource 'tempo change' are specific, and the examples distinguish it from sibling tools that deal with layers, scales, or project management.

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?

Provides clear use cases like 'speed up when entering boss phase 2' and 'slow down for tension before a climax', indicating appropriate contexts. However, it does not explicitly mention when not to use or offer alternative tools.

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