motion studio stop preview

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

Annotations already declare idempotentHint=true and destructiveHint=false. The description adds specific behavioral detail: it removes the clone and effects, which are temporary artifacts. This goes beyond the annotation hints and gives the agent a concrete sense of what will happen. It does not mention failure cases or prerequisites, but for a simple stop operation this is adequate.

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?

A single, front-loaded sentence that conveys the essential purpose and behavior with zero filler. Every word adds value.

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?

Given the presence of an output schema (which need not be explained in the description), the simple optional parameter, and the idempotent non-destructive annotations, the description fully covers what an agent needs to call this tool correctly. There is no missing context about return values or edge cases that would hinder usage.

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 schema already provides full documentation for the single parameter, sessionId, including its purpose and when it is required. The description adds nothing beyond that. With 100% schema coverage, the baseline of 3 is appropriate.

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 ('Stop the temporary preview') and the resource ('its clone and effects'). It is specific and distinct from sibling tools like motion_studio_preview, which starts a preview, and motion_studio_sessions, which manages sessions. The verb and object are 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 context is clear: use this to end a preview that was started with motion_studio_preview. However, there is no explicit mention of when NOT to use it or alternatives, though the sibling list makes the intended pairing obvious. It gives clear context without explicit exclusions.

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