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

Annotations only declare the generic mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false). The description adds genuinely useful context beyond that: what gets carried over (steps and inputs) and, critically, the post-condition that the copy is neither deployed nor scheduled, which tells the agent the new entity is inert.

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 short sentences with the essential scope up front and the non-obvious post-condition second. No filler, no restatement 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?

For a simple two-parameter copy tool this covers the core, but with no output schema the description should say what comes back (e.g., the new workflow's id) and whether the source workflow_id must be readable by the caller. Those gaps matter for an agent chaining a deploy or update after duplication.

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 50%: the 'name' parameter already documents its (Copy) default in the schema, while 'workflow_id' has no schema description. The phrase 'under a new name' reinforces the name semantics but the description never states that workflow_id is the source to be duplicated, leaving half the parameter meaning to inference.

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 a workflow') and scopes the payload ('steps and inputs') as well as the naming behavior. It is unambiguous against resource-specific siblings like deploy_workflow or get_workflow, though it never names an alternative it might be confused with.

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 duplication use case is implied by 'Copy a workflow ... under a new name', but there is no explicit when-to-use, no prerequisites (e.g., source must exist or be readable), and no statement of when to use update_workflow or duplicate_agent instead.

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