stop_clip

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

With no annotations provided, the description carries full burden. It only restates the action ('Stop playing a clip') without disclosing behavior such as whether the clip resets position, what happens if the clip is already stopped, or if it affects only that clip slot.

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 two sentences plus a focused parameter list. It is immediate, scannable, and free of filler, earning its place.

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 clip-stop operation with no output schema or annotations, the description covers the core action and parameter meanings. It lacks edge-case context, but the tool's simplicity makes this acceptable.

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 input schema only declares integer titles, so the description's parameter lines add essential meaning. It explains track_index as the track containing the clip and clip_index as the clip slot within that track, fully compensating for the 0% schema 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 states 'Stop playing a clip' with a specific verb and resource. It clearly distinguishes from related tools like stop_playback (stops transport), stop_scene, and stop_all_clips, which all stop different targets.

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 provides no guidance on when to use this tool versus alternatives such as stop_playback or stop_all_clips. It does not clarify whether to use this for session-view clip slots or other contexts.

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