transport_set_tempo

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

Discloses use of processRECEvent for undo history, but fails to mention other behavioral traits like impact on playback, required project state, or immediate effect. With no annotations, more disclosure is needed.

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 concise sentences with front-loaded purpose. No redundant information.

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?

Omits important context such as valid BPM range, effect on playback, and whether it is a global setting. For a state-mutating tool, this is insufficient.

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?

Parameter 'bpm' has no schema description and the tool description adds no extra meaning beyond the name. No range, validation, or examples provided, despite 0% schema 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?

Clearly states 'Set the project tempo in BPM', specifying the verb, resource, and unit. Differentiates from sibling transport_tap_tempo by omitting tap functionality, but doesn't explicitly distinguish from other tempo-setting methods.

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 guidelines on when to use this tool versus alternatives like transport_tap_tempo. Missing context for appropriate usage scenarios.

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