stop_clip

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

With no annotations, the description must fully convey behavior. It states the tool stops a clip but does not explain edge cases (e.g., if clip is already stopped, queued, or if playback state is affected elsewhere). No side effects or permissions are noted.

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 short and front-loaded with the core action. The parameter list is clear, though it redundantly repeats 'Parameters:' before listing. Overall, it is efficient and easy to scan.

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?

The tool is simple, but the description omits context about which view (session/arrangement) it applies to and any return behavior. Given no output schema and no annotations, additional completeness would be beneficial, but the current description is minimally 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 schema provides no descriptions for track_index and clip_index (0% coverage). The description explicitly links track_index to 'the index of the track containing the clip' and clip_index to 'the index of the clip slot containing the clip', adding crucial meaning beyond the schema's types.

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 succinctly states 'Stop playing a clip,' a specific verb-resource combination. It clearly distinguishes from sibling tools like 'fire_clip' (start playing), 'stop_all_clips', and 'stop_playback' (global 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?

No guidance is provided on when to use this tool versus alternatives such as 'stop_all_clips' or 'continue_playback'. There is no mention of prerequisites or context (e.g., session vs arrangement view).

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