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

Goes far beyond the thin annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false). It discloses the naming convention ("Copy of <name>"), exactly what is copied (live agents/builds, empty queues, routing, handovers, Memory under conditions), that triggers/schedules are copied switched off, that other members' triggers are excluded, and that cases/run history are not copied. That is unusually rich mutation disclosure.

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?

Dense and long, but essentially every clause (naming, copied artifacts, trigger state, exclusions, restrictions) carries decision-relevant information, and the primary action is front-loaded. Slightly run-on as a single block, but not padded.

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 no-output-schema, single-parameter mutation tool the behavioral picture is close to complete. The one omission is what the call returns (e.g. the new automation's id), which would help an agent chain follow-up calls, but the copy semantics themselves are fully covered.

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?

Only one parameter (automation_id), and schema description coverage is 100%, so the schema already documents it fully. The description adds nothing about the identifier itself; per the high-coverage baseline this is a 3.

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) and then enumerates precisely what the copy does and does not contain. An agent can distinguish it from siblings like duplicateAgent or duplicateClarityProcess purely from the text.

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 supplies strong exclusion rules (Module demos and Module automations with Policy questions can't be duplicated), which is real usage guidance. However, it never names an alternative tool or states positive when-to-use conditions relative to createAutomation or the other duplicate* siblings, so routing is only implied.

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