stop_scene

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

No annotations are provided, so the description carries the full burden. 'Stop all clips' is straightforward, but the description does not disclose potential side effects (e.g., does it reset clip positions? affect playback state?). It minimally conveys the action without deeper behavioral context.

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 extremely concise: two short sentences that immediately state the action and list the parameter. Every word is meaningful, and the structure is front-loaded.

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 tool with one parameter, no output schema, and no annotations, the description is incomplete. It fails to explain what 'stop' entails (e.g., does it stop playback of clips? do they reset to start?), and the parameter explanation is minimal. More context is needed for a clear understanding.

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 the description must compensate. It only repeats the parameter name ('scene_index') and its role ('The index of the scene to stop'), adding no extra meaning such as valid range, example, or behavior when invalid. This adds minimal value over the schema.

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 'Stop all clips in a scene,' using a specific verb ('Stop') and resource ('clips in a scene'). This distinguishes it from sibling tools like 'stop_clip' which stops a single clip, and 'fire_scene' which fires a scene.

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 usage guidance is provided. The description does not indicate when to use this tool versus alternatives like 'stop_clip' or 'stop_playback,' nor does it mention prerequisites or context.

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