stop_clip

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

No annotations are provided, so the description carries full burden. It only states 'Stop playing a clip' without disclosing side effects, prerequisites (e.g., clip must be playing), or what happens if already stopped.

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?

Description is concise, with the action front-loaded. Parameter descriptions are briefly listed. Could be more structured, but for a simple tool it is adequate.

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 description is mostly complete. However, it lacks mention of return values, error conditions, or behavior when the clip is not playing. Siblings like fire_clip might need similar treatment.

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 adds meaning to both parameters ('The index of the track containing the clip' and 'The index of the clip slot containing the clip'), complementing the schema which only provides type and title. Schema coverage is 0%, so description compensates well.

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?

Description clearly states 'Stop playing a clip.' It uses a specific verb-resource pairing and distinguishes from sibling tools like fire_clip (which likely starts a clip) and stop_playback (which stops overall playback).

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 on when to use this tool vs. alternatives. For example, it does not explain when to use stop_clip instead of stop_playback or fire_clip to stop a clip.

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