stop_clip

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

No annotations are provided, so the description must disclose behavior. It only states 'Stop playing a clip' with no mention of side effects, what happens if the clip is already stopped, or errors on invalid indices. It does not clarify whether this affects only session clips or also arrangement clips, leaving significant behavioral ambiguity.

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 extremely concise: one sentence for purpose and two bullet points for parameters. Every word earns its place, and the structure is clean and easy to parse. No fluff or 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?

Despite the tool's simplicity, the description is thin. It lacks any behavioral notes, error handling, output description, or relation to sibling tools. With no annotations and no output schema in the visible definition, the description should carry more weight to fully specify the tool's behavior.

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 Args section explicitly defines both parameters as zero-based indices for track and clip slot, which adds meaningful information beyond the bare schema (integer types, titles). This clarifies the expected input format, though it does not cover edge cases or value ranges.

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 action with a specific verb and resource: 'Stop playing a clip.' It is distinct from siblings like stop_all_clips and stop_playback, though it does not explicitly differentiate itself from them. The meaning is unambiguous with the given track and clip indices.

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?

There is no guidance on when to use this tool versus alternatives like stop_all_clips or stop_playback. The description does not mention prerequisites, such as the clip needing to be in the session view or currently playing, nor does it indicate when it would be inappropriate to use.

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