set_live_tempo

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

No annotations provided, so the description must convey behavioral traits. It only states the action without disclosing side effects (e.g., affects playback), permissions needed, or limits. Minimal transparency beyond the basic 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?

Extremely concise: a one-liner plus structured parameter explanations. No wasted words. Information is front-loaded, making it easy to parse.

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?

Has an output schema (content unknown) so return value explanation is not required. However, the description omits any mention of what happens after setting (e.g., immediate playback change). Adequate but could be more comprehensive about effects.

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 carries the burden. It adequately explains each parameter: measure is 1-indexed, bpm is beats per minute, text is optional with examples. Adds meaningful semantics beyond schema titles.

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 the tool sets tempo in a live score. The verb 'set' and resource 'tempo' are explicit. It differentiates well from sibling tools like set_live_barline or set_live_key_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 guidance on when to use or alternatives. The description only lists parameters without context about prerequisites or when not to use. For a simple tool this may be acceptable, but it lacks explicit usage guidelines.

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