Get Cloudflare Zone

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, yet the description still adds real value: it explains the drift failure mode and names two concrete response fields (live public nameservers, nameserversDrifted). It doesn't cover behavior when the zone is absent or unauthenticated, keeping it below a 5.

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 with the purpose front-loaded and no filler. The drift explanation and return-field sentence overlap slightly in motivation, but each still carries distinct information.

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 steps up to disclose the meaningful return values and the drift semantics, and the single param is fully covered by schema. An agent has everything needed to call it correctly and interpret the result.

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?

Only one parameter with 100% schema description coverage, so the schema already documents 'domain'. The description adds scenario context but no syntax or format detail beyond the schema; baseline 3 is appropriate.

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) and resource (Cloudflare zone for a domain) plus the fields returned (status, paused, nameservers, activation date). It also distinguishes itself from the cached Porkbun queue row, which lets an agent separate it from siblings like get_cloudflare_queue.

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?

Clearly frames when to use this over the cached queue data: when nameservers may have been repointed and the Porkbun row may be stale. The alternative is described by concept ('Porkbun's queue row') rather than by tool name, so the routing cue is strong but not literally mapped to a sibling identifier.

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