duplicate_scene

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

Annotations already indicate nondestructive behavior (destructiveHint=false). The description adds that it duplicates clips, but does not disclose whether automation, effects, or routing are copied. Some behavioral context is missing.

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 sentence, which is concise, but it omits critical details limiting its effectiveness. It is front-loaded but under-informative.

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?

While the tool is simple with one parameter and has an output schema, the description does not clarify where the duplicated scene is placed (e.g., after original, at end) or any side effects. This leaves contextual 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?

The schema has 0% description coverage, so the description must compensate. However, it does not explain the scene_index parameter's format, range, or how to determine it. The name alone is insufficient for proper usage.

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 'Duplicate' on the resource 'scene with all its clips' and adds the outcome 'instant section variation', distinguishing it from siblings like create_scene or delete_scene.

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 create_scene, fire_scene, or delete_scene. The agent receives no context on appropriate scenarios or prerequisites.

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