duplicate_clip

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

No annotations are provided, so the description carries the full burden. It discloses the destination (next empty slot) but omits important behavioral details such as what happens if no empty slot exists, whether it overwrites, or what the function returns. For a mutating operation, this is a significant transparency 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 concise, with the main action front-loaded in the first sentence and parameter explanations listed neatly. No waste or redundancy; every sentence earns its place.

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 simple nature of the tool and lack of output schema, the description is minimally adequate but still leaves gaps: no mention of error behavior, prerequisites (e.g., track must exist), or whether the operation is undoable. It is not fully complete for an agent to reliably invoke in all scenarios.

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%, but the description compensates by explicitly explaining both parameters: track_index is 'the index of the track containing the clip' and clip_index is 'the index of the clip slot containing the clip.' This adds clear meaning absent from 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 clearly states the verb 'Duplicate' with resource 'clip' and scope 'to the next empty slot,' making it specific and distinct from sibling tools like create_clip or duplicate_scene. The action and target 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 description implies usage when a user wants to copy a clip to an empty slot, but it does not explicitly state when to use it over alternatives like create_clip, nor does it mention exclusions or prerequisites. No when-to-use or when-not-to-use guidance beyond the basic purpose.

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