Get Cloudflare Domain Status

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds real behavioral value beyond that: it discloses the return payload (zone id, replaced nameservers kept for undo) and the NOT_QUEUED sentinel for unqueued domains.

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 sentences, no waste, with the scope constraint and purpose front-loaded before the return-value detail. Every clause 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?

With no output schema, the description must carry return-value meaning, and it does name the key fields plus the NOT_QUEUED case. It stops short of describing the full status enumeration or the error/missing-domain behavior, leaving a small gap.

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% for the single 'domain' parameter, so the schema already documents it. The description adds no format, casing, or validation detail beyond what the schema supplies, matching the baseline for a fully covered parameter.

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 (get), resource (Cloudflare move status) and narrows scope to ONE domain, which cleanly separates it from batch siblings like get_cloudflare_queue and get_cloudflare_zone. The two key payload fields are named, so an agent knows what it retrieves.

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?

The NOT_QUEUED sentence implies when the tool is meaningful (a domain that has been queued for a Cloudflare move), but there is no explicit guidance on when to use this versus get_cloudflare_queue, get_cloudflare_zone, or preview_cloudflare_move. Usage is inferable, not stated.

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