Retry Cloudflare Domain

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

Annotations already declare destructive=true, readOnly=false and idempotent=true, so the safety profile is partly carried elsewhere. The description still adds real value by disclosing the specific failure modes and that the returned message identifies which one triggered, plus the DNSSEC caveat about repeat skips.

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?

Three sentences, zero filler, front-loaded with the operation and followed by the blocking conditions and the remediation hint. Every sentence earns its place.

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?

No output schema exists, and the description compensates by explaining that failure messages name the cause. For a 2-parameter mutation this is nearly complete; the only minor gap is silence on what dry_run returns or how it interacts with the retry flow.

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% (domain and dry_run both documented), so the schema does the heavy lifting and baseline is a 3. The description adds a little context around the domain's re-queue condition but says nothing about dry_run, which would have added meaning beyond the schema.

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 ('Re-queue') plus resource ('domain') and the exact condition that qualifies it ('whose Cloudflare move failed or was skipped'). This distinguishes it clearly from siblings like rollback_cloudflare_domain and connect_domains_to_cloudflare without needing to open 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 strong when/when-not guidance by enumerating the failure preconditions (already connected, in progress, no longer in account) and advising to fix the root cause first. It stops short of naming the sibling commands to use in those alternative situations, but the routing context is clear.

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