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

Goes well beyond the annotations: it specifies that queues are copied empty, that the caller's triggers/schedules are copied switched off, that other members' triggers/schedules are excluded, that Memory is copied only when the team holds Memory and the agent has it on, and that cases and run history are not copied. This is exactly the kind of side-effect detail an agent cannot infer from readOnlyHint/destructiveHint.

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?

A single front-loaded sentence that names the operation and outcome first, then the copy semantics, then the exclusions. Despite its length, every clause conveys distinct, decision-relevant information with no filler.

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 mutation with no output schema, the description covers what is and isn't copied thoroughly. The only gap is that it never states what the call returns (presumably the new automation's id), which an agent needs to subsequently operate on the copy.

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 description coverage is 100% and there is a single well-documented parameter (automation_id), so the schema already carries the load. The description implies the parameter is the source automation but adds no format or semantic detail beyond it, making the baseline 3 appropriate.

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?

States a specific verb (duplicate) and resource (automation), plus the concrete naming outcome ('Copy of <name>'). It distinguishes itself from sibling duplication tools like duplicateAgent and duplicateClarityProcess by enumerating exactly which internal artifacts of an automation are carried over.

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?

Usage is implied: an agent should reach for this when it wants a copy of an existing automation rather than building one from scratch with createAutomation. However, there is no explicit when-to-use/when-not statement and no alternative named (e.g. createAutomation vs duplicate), so selection guidance is left to inference.

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