fire_clip

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

Annotations idempotentHint=false and destructiveHint=false are not contradicted. The description adds important behavioral context: launching takes Session control, replaces other clips, and may retrigger an already-playing clip.

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?

Three sentences, front-loaded with purpose, then details and alternatives. No unnecessary words or repetition.

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?

The tool is simple, has output schema, and the description covers preconditions, behavior, and alternatives, making it complete for its complexity.

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 100% with descriptions for both parameters. The description does not add extra parameter meaning beyond the schema, so baseline 3 is appropriate.

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 starts with 'Launch one existing Session-view clip using Live's launch quantization,' clearly stating the verb and resource. It distinguishes from siblings by mentioning fire_scene and continue_playing.

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?

The description explicitly states when to use fire_clip ('The slot must contain a clip'), describes its behavior, and provides alternatives: 'Use fire_scene to launch a whole row, or continue_playing for transport only.'

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