duplicate_clip_to_track

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states the action ('duplicate') without explaining effects (e.g., whether the original clip persists, if metadata is copied, error conditions, or response format). For a mutation tool with zero annotation coverage, this is a critical gap.

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 extremely concise at three words, with no wasted text. However, this brevity comes at the cost of underspecification—it's concise but incomplete. Given the scoring criteria focused on efficiency, it earns full marks for zero redundancy.

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 mutation tool with 3 undocumented parameters, no annotations, and no output schema, the description is severely inadequate. It fails to explain behavior, parameter meanings, usage context, or expected outcomes, leaving the agent poorly equipped to invoke it correctly.

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 0%, meaning all three parameters (clip_id, time, track_id) are undocumented in the schema. The description adds no parameter information beyond what's inferred from the tool name (e.g., that clip_id identifies the clip to duplicate). It doesn't explain parameter roles, formats, or constraints (e.g., time units, track_id validity).

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 'duplicate clip to track' is essentially a tautology that restates the tool name without adding meaningful clarification. While it identifies the action (duplicate) and target resources (clip, track), it doesn't specify what duplication entails (e.g., creating an identical copy at a new position) or distinguish it from similar sibling tools like duplicate_clip_loop or duplicate_clip_region.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., existing clip/track), use cases (e.g., arranging content), or differentiate from sibling duplication tools (duplicate_clip_loop, duplicate_clip_region), leaving the agent with no context for selection.

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