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

No annotations are provided, so the description carries the full burden. The key behavioral disclosure — 'Media documents are referenced, not copied' — is valuable since it tells the agent the duplication is shallow, avoiding wasted copies. However it says nothing about permissions, side effects on the source shot, or whether the new shot gets a fresh ID.

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 sentence that front-loads the action and lists the carried-over attributes compactly, with the shallow-copy caveat as a tight second sentence. Zero 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?

Adequate for a shallow-copy tool with a fully-covered schema and no output schema. It does not cover where the duplicate lands by default, required permissions, or return value, which for a creation tool with no annotations leaves gaps.

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 the schema already documents all five parameters including the optional destination sceneId and order. The description adds nothing about parameter behavior, so baseline 3 applies.

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+resource ('Duplicate a shot') and enumerates exactly which attributes carry over (media refs, trimming, playback, frame-linking, prompts, dialogue, tags). It is immediately distinguishable from update_shot, create_shot, and split_shot.

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?

Usage is implied by the verb, but there is no explicit when-to-use vs create_shot (which also produces a new shot) or split_shot. The default destination (same scene as source) and required workspace/edit context are not stated.

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