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 of behavioral disclosure. It only states the core action and does not cover side effects, reversibility, safety, or return values. For a mutation-like action, this is opaque.

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 a single, front-loaded sentence followed by a minimal parameter list. No wasted words; it is appropriately concise for a simple tool.

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, the short description is mostly adequate, but it lacks any guidance on scene identification or comparison with stop_clip. The absence of an output schema reduces the need for return-value documentation, but the description could still be more helpful.

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 description repeats the schema's parameter name with a minimal gloss ('the index of the scene to stop') but adds no valuable context like zero-based indexing, valid range, or relationship to other scene-related APIs. With 0% schema description coverage, this is insufficient.

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 uses a specific verb ('stop') and resource ('scene'), stating it stops all clips within a scene. This clearly distinguishes it from siblings like stop_clip (single clip) and fire_scene (launch 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?

The description implies its use case (stopping all clips in a scene) but provides no explicit guidance on when to choose it over stop_clip or fire_scene. No alternatives or exclusions are mentioned, leaving the agent to infer from the name.

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