Clone a public Wiro workflow

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

Goes well beyond annotations by disclosing that it is free, that each call makes another copy (reinforcing non-idempotency), and that protected workflows retain hidden steps — runnable and retitleable but not editable. That protected-workflow caveat is critical behavioral context an agent cannot infer from readOnlyHint=false or idempotentHint=false.

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, zero waste. The core action is front-loaded, the cost note is early, and the when-to-use guidance and protected-workflow caveat follow in logical order.

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?

Complete for this tool: an output schema exists so return values need not be described, the single parameter is fully covered by the schema, and the description supplies the behavioral nuances (free, non-idempotent, protected-step limitation) an agent needs to call it correctly.

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 100% — the slug parameter is fully documented in the schema including that it accepts a full slug or page URL from list_workflows scope 'public'. The description adds no additional slug syntax detail, so 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?

The opening sentence gives a specific verb and resource: copy a published gallery workflow into the API key's workspace as a private workflow. This clearly distinguishes it from create_workflow (new), run_workflow (execute), and get_workflow (read).

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?

Explicitly states when NOT to clone: 'You do not need a copy just to run a public workflow; clone it to keep it or to edit it.' This names the two conditions that justify cloning, routing the agent cleanly away from clone when run_workflow suffices.

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