Get Cloudflare Domain Status

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), but the description still adds real behavioral context: it exposes the zone id once created, discloses that Porkbun's replaced nameservers are retained so the move can be undone, and defines the NOT_QUEUED sentinel for unqueued domains. That return-shape detail matters because there is no output schema.

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?

Two dense sentences, no filler, with the core action front-loaded and the parenthetical about retained nameservers earning its place by explaining why the data is returned.

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 one-parameter, read-only status probe with full annotation coverage, the description covers purpose, scope, and key return values, including the NOT_QUEUED case. Without an output schema it would benefit from stating what else a queued domain's response contains (progress/state fields), but nothing essential to correct invocation 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 coverage is 100% and the single required parameter "domain" is already documented as "Domain to check." The description adds only the cardinality constraint ("ONE domain"), which is a useful but minor supplement over 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 and resource ("Get the Cloudflare move status") and pins the scope with "for ONE domain," which separates it from list_cloudflare_inventory and the sibling read tools get_cloudflare_connection, get_cloudflare_queue, and get_cloudflare_zone. An agent can tell what it returns (zone id, replaced nameservers) without opening another 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?

Usage is only implied: you call it to check move status for a single domain, and the note that it returns NOT_QUEUED for never-queued domains hints at an edge case. It names no alternatives (preview_cloudflare_move, get_cloudflare_connection, retry_cloudflare_domain) and gives no explicit when-not-to-use condition.

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