stop_clip

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

Annotations already signal this is not read-only and not destructive, and the description adds the dual plan/stop behavior plus exact-slot scoping. However, it does not disclose that planning is side-effect-free or that execution requires a confirmation token, which are key behavioral details.

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 with no filler. It loses a point because the phrase 'Plan or stop' is compact but does not make the two-phase workflow immediately obvious.

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 schema carries most of the parameter semantics, but the description omits the overall plan/confirm workflow, the role of expectedStateVersion, and when to choose this tool over siblings like stop_all_clips or transport_stop. An agent can infer much from the schema, but the description alone is thin.

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 100%, so all six parameters are already documented in the input schema. The tool description adds no additional meaning beyond what the schema provides.

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 names a specific action ('Plan or stop') and a specific resource ('one exact Session clip slot'), which is clear. It implies a distinction from stop_all_clips and arrangement-clip tools, but does not explicitly name any sibling or alternative.

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 when-to-use guidance is provided. The description does not mention alternatives like stop_all_clips, launch_clip, transport_stop, or explain when to plan versus when to actually stop a clip.

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