stop_all_clips

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states that it stops all playing clips, but does not mention side effects such as whether transport continues, whether clip positions reset, or whether it affects only session view (though 'session' is implied). The behavior is minimal and lacks context beyond the action itself.

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, concise sentence that is front-loaded with the action. It contains no filler or redundant words, and every word contributes to understanding. Perfectly sized for a simple 0-parameter 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?

For a simple 0-parameter command with an output schema, the description is largely complete. It specifies 'session' to scope the action and clearly conveys what happens. However, it could be slightly more complete by clarifying that it does not stop transport (since 'stop_playback' exists as a sibling), but given the simplicity, it is adequate.

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 tool has zero parameters, so per the rubric the baseline is 4. The description does not need to add parameter semantics since there are none. The schema coverage is 100% (trivially), and the description adds no conflicting information.

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 a specific action: 'Stop all playing clips in the session.' It identifies the verb (stop), the resource (all playing clips), and the scope (in the session). This distinguishes it from siblings like 'stop_clip' (single clip) and 'stop_playback' (transport stop).

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 usage when you want to stop all session clips, but it does not explicitly state when to use it over alternatives like 'stop_clip' or 'stop_playback'. There is no mention of exclusions or conditions. This is implied usage rather than explicit guidance.

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