stop_clip

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

With no annotations, the description carries full burden but only states the action 'stop'. It does not disclose side effects (e.g., does it reset clip position?), requirements (e.g., clip must be playing), or what happens if the clip is 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?

The description is a single sentence with no fluff. It is appropriately sized for the tool's simplicity.

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 and the presence of an output schema, the description is minimally adequate. However, it lacks parameter descriptions and behavioral context that would help an agent use it correctly, especially without annotation support.

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?

Schema description coverage is 0%, yet the description adds no meaning to the parameters 'track_index' and 'slot_index'. Terms like 'slot_index' are domain-specific and could benefit from clarification (e.g., zero-based indexing).

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 'Stop a playing clip on a specific track' clearly states the verb 'stop' and the resource 'clip on a specific track'. It is specific and distinguishes from sibling tools like 'stop' (stops overall playback) and 'fire_clip' (starts clip), but does not explicitly differentiate from 'delete_clip' or others.

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. For example, it does not specify that this stops a specific clip while leaving other clips or the overall playback unaffected, nor does it mention prerequisites like the clip must be playing.

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