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

Adds genuinely non-obvious behavior beyond the annotations: the copy is created inactive and nothing executes until isActive is set via automation_upsert. It leaves out whether repeated calls create multiple copies (annotations say idempotentHint=false) and what the call returns, which matters for chaining.

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?

Three short sentences, front-loaded with the outcome ('new inactive draft'), followed by the safety implication and the use case. Nothing is redundant.

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 single-parameter mutation this covers the safety story well, and the annotations carry the write profile. However, the description tells the agent to activate the copy via automation_upsert without saying whether this tool returns the new automation id — a real gap for chaining, and there is no output schema to fall back on.

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 single parameter has 100% schema coverage and already points to automation_list as the source of the id. The description adds no format, default, or constraint information beyond the schema, so the baseline of 3 applies.

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?

'Copy an automation into a new inactive draft' is a specific verb+resource+result-state, not a restatement of the name. An agent can immediately distinguish this from automation_upsert and automation_get in the sibling list.

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?

It gives a clear use case ('try a change without touching the automation currently handling live events') and names automation_upsert as the step that activates the copy. It stops short of explicit exclusions (e.g. when to edit in place instead of duplicating) but the selection context is unambiguous.

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