duplicate_layer

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

With no annotations, the description must fully disclose behavior. It covers inheritance of opacity and blend mode, and placement options, but omits details like error handling, behavior if layer not found, or effects on selection. Some behavioral aspects remain unspecified.

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 compact and well-structured: a clear purpose statement followed by behavioral notes and parameter documentation. Every sentence adds value, though the Args section could be more concise.

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 moderate complexity of duplicating layers across frames, the description covers key aspects: what is duplicated, inheritance, placement. It lacks details on return values, error conditions, and naming conflict resolution, but is adequate for a tool with no output schema.

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?

Although the schema has 0% description coverage, the description's Args block provides clear definitions for each parameter, including defaults and path syntax. This compensates well for the schema gap, though some parameters like 'new_name' could be more detailed about default naming.

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 layer with all its cels across every frame,' specifying the exact verb and resource. It distinguishes from sibling tools like copy_cel or duplicate_frame by clarifying it duplicates entire layers with all frames.

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 explains the default placement and the group parameter but does not explicitly state when to use this tool versus alternatives like 'copy_layer' or 'duplicate_frame_range'. There's no guidance on prerequisites or when not to use it.

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