clips_stop

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

The annotations already establish that this is a non-read-only, idempotent, non-destructive operation. The description adds the important behavioral detail that omitting track stops all tracks, but it does not describe any additional side effects, return behavior, or prerequisites.

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 definition is a single front-loaded sentence with no wasted wording. It communicates the core action and the all-tracks default efficiently.

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 one-parameter mutation with annotations covering safety and no output schema, the description is largely complete. Its main gap is the lack of explicit comparison with alternative clip or transport controls.

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 coverage is 100%, and the schema already explains UUID versus 0-based index semantics. The description adds meaning beyond the schema by stating that no track means every track, which clarifies the optional parameter's default scope.

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 uses a specific verb and resource: stopping the session clip of one track or all tracks. It is clear and scoped, but it does not explicitly distinguish itself from nearby siblings such as clips_launch, clips_clear, or transport_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?

It explains the effect of omitting track (stop every track) and supplying one (stop that track), which is useful invocation guidance. However, it gives no explicit when-to-use guidance versus alternative clip or transport tools, and no exclusions.

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