stop_clip

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

With no annotations, the description must disclose behavioral nuances but only states 'Stop playing a clip.' It does not explain whether the clip is reset to start, whether it only affects a playing clip, or what side effects might occur. This is minimal and lacks depth expected for a control 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 very short and front-loaded with the main action, making it easy to parse. The parameter list is somewhat redundant with the schema, but it adds minimal clarification without excessive length.

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 description is sufficient for a simple action, providing the essential operation and parameter meanings. However, it lacks context about when to choose this over stop_playback, and there is no information about return values or side effects. Given the simplicity of the tool, this is adequate but with clear gaps.

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 includes parameter explanations that add meaning beyond the schema's bare integer types. It clarifies that track_index is the track containing the clip and clip_index is the clip slot, which helps the agent correctly identify the target. Although the schema itself has no descriptions, the tool description compensates effectively.

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 'Stop playing a clip' with a specific verb and resource, which identifies the tool's core function. It does not explicitly differentiate from sibling tools like stop_playback, but the clip-specific wording makes the scope reasonably clear.

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_playback or fire_clip. There are no usage scenarios, prerequisites, or exclusions mentioned, leaving the agent without context for tool selection.

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