Connect Domains To Cloudflare

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

Annotations declare destructive=true and idempotent=true, but the description adds far more: it is ASYNCHRONOUS and a success means QUEUED not connected, results are per-domain with individual reasons, a non-empty `skipped` is normal rather than an error, and eligibility is re-checked before each domain acts. These are exactly the behavioral traits annotations cannot express.

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?

Dense but front-loaded: the async/queued caveat and the poll-it-next instruction come early where they matter most, and each subsequent sentence adds a distinct fact (per-domain results, skipped-is-normal, eligibility re-check, dry_run, domain cap). No filler.

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?

There is no output schema, yet the description tells the agent the exact result shape (`queued`, `skipped`, `alreadyQueued`) and how to interpret it, plus the async handoff to get_cloudflare_queue. Nothing an agent needs to invoke and correctly interpret this tool is missing.

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 both parameters are already documented in the schema. The description's dry_run guidance and 500-domain limit largely restate the schema's description and maxItems constraint rather than adding new semantics, so the 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?

States a specific action (queue domains to move into the customer's own Cloudflare account) and then spells out the mechanics: Porkbun creates the zone, copies DNS records, repoints registry nameservers. This is clearly distinguishable from siblings like preview_cloudflare_move or retry_cloudflare_domain.

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 names the prerequisite (Cloudflare account must be connected first, see get_cloudflare_connection), the follow-up action (poll get_cloudflare_queue), the preview path (use dry_run), and the boundary (max 500 domains per call). When-to-use and what-comes-next are both covered.

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