fire_scene

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

The description discloses the primary behavioral effect (playing all clips in the row) but omits potential side effects, prerequisites, or behavior when a scene is already playing. With no annotations, the description carries the full burden, and while it conveys the core action, it lacks depth.

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?

The description is concise: two sentences plus a parameter list. Every word is necessary, and the structure is clean and easy to scan.

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?

For a simple tool with one parameter and no output schema, the description is largely complete. It defines the action and parameter, though it could mention the relationship to selecting or stopping scenes for fuller context.

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?

The schema has no parameter descriptions, and the description adds 'scene_index: The index of the scene to fire,' which explains the parameter's purpose. However, it does not clarify indexing base (0-based vs 1-based) or any bounds, so the added meaning is minimal.

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 fires (triggers) a scene to play all clips in that row. This distinguishes it from sibling tools like select_scene, stop_scene, and fire_clip by specifying the action and scope.

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 versus alternatives such as fire_clip or select_scene. The intended use is implied by the description but not stated as a recommendation or exclusion.

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