fire_scene

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

No annotations provided, so description must disclose behavior. Only states it 'launches all clips,' but does not mention side effects like stopping other clips, error handling for invalid index, or any required conditions.

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: first states purpose, second lists parameter. No unnecessary words, front-loaded, efficient.

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?

Output schema exists, so return values need not be described. Basic behavior covered, but missing mention of prerequisites (scene must exist) or error cases. For a simple tool, mostly complete.

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?

Only one parameter, and schema coverage is 0%. Description adds '0-based' which is crucial for correct usage. Could be improved with valid range, but adequately compensates for schema's lack of description.

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 verb 'Fire (trigger)' and resource 'scene', explaining it launches all clips in the scene's row. Distinguishes from siblings like fire_clip and fire_selected_scene by specifying scene_index parameter.

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?

Usage is implied (trigger a specific scene by index), but no explicit guidance on when to use this vs. alternatives like fire_selected_scene. No 'when not to use' or prerequisite advice.

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