set_scene_tempo

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

No annotations are provided, so the description carries full burden. It clarifies that bpm=0 means 'no tempo change' but doesn't disclose side effects, whether it overrides global tempo, or if it affects currently playing scenes. Significant gaps in behavioral transparency.

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: two-line description plus a compact parameter list. Front-loaded with the core action. No unnecessary words, every sentence earns its place.

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's simplicity and existence of an output schema (though not shown), the description is adequate but missing details like return value, prerequisites (e.g., scene existence), or error conditions. Not fully complete for an agent to use confidently.

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%, so description must compensate. It adds meaning by noting scene_index is 0-based and bpm=0 indicates no tempo change. However, it doesn't specify allowed BPM range or what 'scene index' refers to in the context of the application.

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 'Set the tempo for a specific scene (scene-based tempo changes).' The verb 'set' and resource 'scene tempo' are specific, and it distinguishes from the sibling 'set_tempo' which likely sets global tempo.

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 guidance on when to use this tool vs alternatives like 'set_tempo' or 'tap_tempo'. The description only implies it's for scene-specific changes but doesn't provide concrete scenarios or exclusions.

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