Rollback Cloudflare Domain

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

Goes well beyond the destructiveHint/openWorldHint annotations by disclosing that authoritative DNS for a live domain changes, that the Cloudflare zone is deliberately left in place (and why deleting it is the customer's call), and the three failure conditions. These are exactly the side-effect details an agent needs before invoking a destructive mutation.

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 dense sentences, front-loaded with the action, then the safety warning, then the non-obvious zone-retention behavior, then failure modes. Nothing is wasted or repeated from structured fields.

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 destructive, open-world, idempotent mutation with no output schema, the description covers the effect, the surprising non-effect (zone retained), the confirmation requirement, and the failure surface. An agent can call this correctly and safely without further 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?

Both parameters (domain, dry_run) are already fully described in the schema at 100% coverage, so the description adds no syntax or format detail. Baseline 3 applies; the description's failure conditions implicitly inform when dry_run is useful but do not explain it.

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 ('UNDO a completed Cloudflare move') and the exact resource action: repointing nameservers back to Porkbun to restore the DNS Porkbun still holds. This cleanly distinguishes it from connect_domains_to_cloudflare, disconnect_cloudflare, and retry_cloudflare_domain without opening any schema.

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?

Gives a clear precondition ('a completed Cloudflare move') plus explicit when-not conditions: fails if Porkbun never moved the domain, if it is already back on Porkbun nameservers, or if work is in progress. It also mandates confirming with the user first. It does not name a sibling alternative, which keeps it just below a 5.

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