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

With no annotations, the description carries the full burden. It discloses that the copy starts in draft and that editing/publishing are separate steps, which is useful. However, it does not explain what exactly is copied (nodes, edges, settings), whether the original is modified, or any side effects or permission requirements. This is a moderate disclosure.

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?

The description is compact, front-loading the core purpose, then providing parameter guidance and outcome expectation in three clear sentences. Every sentence adds value with no redundancy.

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?

Given no annotations, no output schema, and incomplete parameter documentation, the description leaves important gaps: it does not clarify the role of flowId, what constitutes a 'copy' (scope of duplication), or any constraints (e.g., uniqueness of newName). An agent could call this tool incorrectly without this information.

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 0%, so the description must explain all parameters. It covers flowName and newName, but completely omits flowId. The description suggests flowName is the identifier, but does not clarify how flowId relates or when to use it. This is a significant gap for an agent.

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 description states a clear action ('Copy an existing flow as a new draft') with specific examples ('duplicate flow X', 'clone the giveaway flow'). It distinguishes from siblings like create_flow and update_flow by making clear this is a copy operation, not a fresh creation.

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 explains how to identify the source (by flowName) and how to name the copy (newName). It also notes that the copy starts as a draft, implying the user must publish separately, which gives context for when this tool is appropriate versus alternatives. However, it does not explicitly mention when NOT to use it or name alternatives like create_flow.

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