duplicate_clip

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

The description does not disclose behavioral traits like whether the target slot is overwritten, whether the clip content is copied or moved, or any side effects. With no annotations, the description carries the full burden but provides minimal behavioral 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 description is a single concise sentence followed by a structured argument list with no redundant text. It is front-loaded with the core action and efficiently organized.

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?

As a mutation operation with no annotations, the description covers parameters but omits important contextual details like overwrite behavior, session vs arrangement scope, and return value semantics. The existence of an output schema isn't leveraged to explain expected results.

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?

All four parameters are explicitly defined as zero-based indices for source and destination tracks/clip slots. This adds meaningful semantics beyond the bare integer schema, fully compensating for the 0% schema description coverage.

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 'Duplicate a clip to another clip slot' with a specific verb and explicit target resource. This distinguishes it from siblings like duplicate_clip_loop by emphasizing slot-based copying.

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?

No guidance is provided on when to use this tool versus alternatives such as duplicate_clip_loop or duplicate_to_arrangement. The description only lists arguments, with no context or exclusions.

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