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

Annotations only declare it is a non-read-only, non-destructive, non-open-world write. The description goes beyond that with real behavioral detail: runs and versions are not copied, post-bound copies retain their post, and next-post flows re-wait. It does not, however, state where the resulting draft surfaces or what identifier comes back.

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?

Two sentences, front-loaded with the core action, then a dense clause covering the three non-obvious copy behaviors. No filler and no repetition of the title.

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?

With no output schema, the description should ideally say what the copy returns (e.g., the new draft's id) for a follow-up enable/publish call. Everything else an agent needs — what is copied, what is not, post binding behavior — is present.

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 67% and the description adds only the optionality of the name ('optionally with a new name'), which the schema already covers with its default hint. The workspaceId guidance lives entirely in the schema, so the description neither compensates nor detracts; baseline 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?

States a precise verb+resource ('Copy an automation as a new draft') and immediately scopes what makes it distinct from create_automation/update_automation by specifying what is carried over (triggers and settings). An agent can distinguish it from its siblings without opening a schema.

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 conveys the semantics of a copy but never states when to prefer this over create_automation or list_automation_templates. Usage is implied by the copy semantics ('same triggers and settings, optionally with a new name') rather than explicitly routed.

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