duplicate_elements

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

With no annotations, the description carries the full burden of disclosing side effects and behavior. It does not state whether the operation creates new elements, leaves originals intact, or affects any related data. It also does not explain the return behavior or potential side effects on selections or groupings.

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, front-loaded sentence with no redundant words. It communicates the core action and a key qualifier efficiently. It is appropriately concise, though a bit more detail could be added without becoming verbose.

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's moderate complexity, no output schema, and no annotations, the description is insufficient. It fails to explain what the operation returns, whether it is destructive, or how the offset parameters behave. Key contextual details that an agent would need for correct use are absent.

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 description offers a minimal hint that offsets are configurable, but it does not explain the parameters at all. With 0% schema description coverage, this is insufficient. The meaning of 'elementIds' is left to inference from its name, and the description adds little beyond the schema's bare property names.

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 tool's purpose: duplicating elements, with the added detail of a configurable offset. The verb 'duplicate' is specific and distinguishes it from sibling tools like create_element or update_element. The 'configurable offset' further specifies the operation's scope.

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. The description does not mention any prerequisites, exclusions, or preferred contexts. It simply states the action without any comparative or situational advice.

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