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

Annotations already establish that this is a non-readonly, non-destructive, idempotent edit. The description adds useful behavioral context beyond that: exactly two adjacent clips are affected, one lengthens and the other shortens, and no other elements move. It does not discuss permissions or edge cases, but the added mutation footprint is meaningful.

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 compact and front-loads the core operation. The closing note about returning the edit result and referring to server instructions is slightly redundant given the output schema, but overall there is little waste.

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 moderately complex edit tool with full schema coverage, rich annotations, and an output schema, the description gives enough core semantics to call it correctly. It could be stronger by stating prerequisites such as the need for a following clip on the same track, but the essential behavior is present.

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 clip_id, to_frame, preview, and timeline_id are already documented. The description clarifies the relationship between clip_id and to_frame by describing the cut between two adjacent clips, but adds no syntax, bounds, or format details beyond the schema.

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 states a specific verb and resource: moving the cut between a clip and the clip immediately after it. The added detail that one clip gets longer, the other shorter, and nothing else moves distinguishes this roll edit from adjacent operations such as trim, slide, or move, even without naming those siblings.

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 description implies when to use the tool by explaining that only the cut point shifts between two adjacent clips, while everything else stays fixed. However, it does not explicitly name alternatives like clip.trim or clip.slide, nor does it state exclusions or prerequisites for choosing this operation.

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