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

Discloses behavior well beyond the annotations: the copy is created TURNED OFF deliberately, with the reason spelled out (two live flows on the same keyword/post would double-DM commenters), plus that run counters and A/B stats reset and that the copy stays in the original's workspace. The annotations only say it is a non-read, non-destructive, non-idempotent write; the description supplies the operational consequences.

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?

Four tight sentences with no filler: purpose first, then the critical off-by-default caveat, then the remediation step, then the stats/workspace note. The most surprising constraint (turned off) is front-loaded rather than buried.

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?

Covers the mutation's side effects, the follow-up call, and state resets, which is thorough for a 3-parameter tool with no output schema. The one gap is that it never says the response yields the new flow's id, which the agent needs to call set_automation_active 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%, so name, flowId and idempotencyKey are already fully documented, establishing a baseline of 3. The description adds only marginal meaning, notably that the copy lands in the same workspace as the original; it does not clarify the idempotency semantics beyond what the schema states.

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 and resource ('Copy an existing flow, graph and all') and immediately scopes the use case ('so you only have to change what differs'). An agent can distinguish this from create_automation or create_automation_from_template 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?

Gives a clear selection condition (copy when most of the flow is reusable) and names the required follow-up step and tool: 'Change what you need, then turn it on with set_automation_active.' It does not explicitly name create_automation as the alternative for building from scratch, so it falls short of full when/when-not coverage.

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