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

Annotations cover the mutation profile (not read-only, not destructive, not idempotent), and the description adds important scope details: all steps and configuration are copied, but connections and sample data are not. This goes beyond annotations and helps the agent understand the effect. It does not mention return values or permissions, so not a 5.

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 three compact sentences, front-loaded with the core action, then the copy scope, then the exclusion. Every sentence earns its place 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?

For a duplication tool with annotations covering safety and a complete input schema, the description covers the key behavioral nuance (what is and isn't copied). Missing details about return value or error conditions are minor given the lack of an output schema, but the definition is nearly complete.

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%, with both parameters well documented, including a note to use ap_list_flows for flowId. The description adds no additional parameter meaning, so the baseline of 3 is appropriate.

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 specific verb (duplicate) and resource (flow), and clarifies that it copies all steps and configuration. However, it does not explicitly differentiate this from sibling tools like ap_create_flow or ap_build_flow, leaving the agent to infer that this is for copying rather than creating from scratch.

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?

Usage is implied: use when you need a copy of an existing flow. There is no explicit guidance on when to choose this over alternatives such as ap_create_flow, nor are any prerequisites or exclusions stated.

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