Duplicate Layer

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

The description discloses that the operation duplicates the layer including its style, which is helpful. However, with no annotations provided, it should mention potential side effects (e.g., creation of a new layer, naming implications). Currently adequate but not thorough.

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, clear sentence with no wasted words. It conveys the essential information efficiently.

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?

For a simple operation with two parameters, the description is mostly complete but lacks context on error handling, naming constraints, or behavior when new_name is omitted. Adequate but with 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?

Schema coverage is 0%, and the description does not explain the parameters. It mentions 'under a new name' but does not clarify that new_name is optional or what happens when null. The parameter semantics are weak.

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 states the action (Duplicate), resource (a layer), and key characteristics (including its style, under a new name). It clearly distinguishes the tool from siblings like add_vector_layer or remove_layer.

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 on when to use this tool versus alternatives or any prerequisites (e.g., the layer must exist). The description lacks context for decision-making.

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