stop_scene

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

With no annotations, the description carries the burden of behavioral disclosure. It states that the tool stops all clips in a scene, which is a meaningful multi-clip action, but does not disclose potential side effects (e.g., playback state, follow actions, invalid index handling).

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 with a clear, front-loaded purpose statement followed by a simple parameter list. It is efficient, though the parameter list could be integrated more elegantly to avoid redundancy.

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 one-parameter tool, the description covers the core action and parameter. However, it lacks details about error handling, prerequisites, or interaction with playback state, making it minimally adequate but not fully 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?

The description's parameter section merely restates the schema title: 'The index of the scene to stop' adds no meaningful detail beyond the parameter name. It does not clarify indexing conventions (e.g., zero-based) or error behavior, so it fails to compensate for the 0% schema description coverage.

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 the specific verb 'stop' and the resource 'all clips in a scene', clearly distinguishing it from sibling tools like stop_clip (single clip) and stop_all_clips (all clips globally).

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 when to use the tool: when you need to stop all clips within a specific scene. However, it does not explicitly mention alternatives or exclusions, so the guidance is implied rather than explicit.

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