moveClip

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that by guaranteeing that clip ids, source ranges, trims, zooms, speed regions, and annotations are all preserved — key reassurance for a reordering mutation. It does not disclose failure modes for invalid ids or missing project context.

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 core action and positioning convention are front-loaded in the first sentence. The preservation sentence and the sibling contrast add length but each carries useful information; minor trimming is possible but nothing is wasted.

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?

With no output schema and a simple three-parameter mutation, the definition covers action, id sourcing, positioning semantics, preservation guarantees and sibling routing. Remaining gaps (auth requirements, error behavior) are minor.

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 only 33%, so the description must compensate, and it does: it explains that ids come from getCurrentDocument (with `index` and `reason` label), and that `beforeClipId` null/omitted means move last. The third parameter, projectId, is already well documented in 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?

States a specific verb and resource: "Reorder a placed clip: move `clipId` so it plays just before `beforeClipId`." It explicitly distinguishes itself from the sibling replaceTimeline, so an agent can route between them without opening either schema.

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?

Gives explicit use cases ("swap these clips", "put X first", "change the clip order") and names the condition that selects the alternative: "replaceTimeline cannot reorder anything." It also states the null/omit convention for placing a clip last.

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