stop_clip

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

The description discloses the core behavior (stopping a clip) but with no annotations, it does not cover prerequisites, error conditions, or side effects. It is minimally transparent for a simple action.

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, front-loaded sentence followed by a concise parameter list. Every word serves a purpose with no redundancy.

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 tool with 2 parameters and an output schema, the description covers the basic action and parameter meanings. However, it omits details like idempotency or what happens if the clip is not playing, which would improve completeness.

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 the two parameters by explaining what each index refers to (track containing the clip, clip slot containing the clip). However, it lacks details like valid ranges or zero-based indexing. With 0% schema coverage, it provides essential but not thorough 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 the verb 'stop' and the resource 'clip', which is distinct from sibling tools like 'fire_clip' and 'stop_playback'. The purpose is unambiguous.

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 implicitly indicates when to use (to stop a specific clip) but provides no guidance on when not to use or alternatives like 'stop_playback'. No exclusions or context are given.

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