duplicate_clip_to

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

The description explicitly mentions that the tool overwrites the destination slot, which is key behavioral information. Annotations only include destructiveHint: false, so the description adds value. However, it does not detail what exactly is copied (e.g., all clip contents) or behavior when source and destination are the same.

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 two sentences long, front-loads the action and resource, and contains no unnecessary words. It is highly concise and well-structured.

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 tool has 4 parameters, no schema descriptions, minimal annotations, and an output schema, the description provides the core behavior but lacks details like prerequisites (e.g., Session view required) or edge cases. It is adequate but not fully complete.

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?

The input schema has 4 integer parameters with 0% description coverage, and the description provides no explanation of them. While tool name and description hint at source/destination roles, the description does not add meaning beyond the schema, missing an opportunity to clarify parameter functions.

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 action 'Copy a Session clip' and the resource (clip). It specifies the ability to copy to any other track/scene slot and that it overwrites the destination, which distinguishes it from sibling duplication tools like duplicate_scene or duplicate_track.

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 for creating variations across tracks and scenes but does not explicitly state when to avoid using it (e.g., for arranging timeline tasks) or mention alternative tools. However, the context of 'cross-track' and 'overwrites' provides reasonable guidance.

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