Get Cloudflare Zone

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuine behavioral context beyond that: it explains why live data can disagree with the stored row and discloses the nameserversDrifted boolean, though it says nothing about auth, rate limits, or freshness guarantees.

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?

Purpose is front-loaded in the first clause and each sentence contributes (what it returns, why drift matters, what the response adds). The drift example is slightly long-winded, but nothing is pure filler.

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?

There is no output schema, so the description carries the burden of describing returns, and it does so by listing status, paused, nameservers, activation date, and the nameserversDrifted flag. Combined with annotations covering safety, an agent has everything needed to call this single-parameter read correctly.

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 baseline is 3. The description only paraphrases the parameter ('a domain's zone') and adds no format or constraint detail beyond what the schema already provides.

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 what CLOUDFLARE ... says about a domain's zone') and enumerates what it returns (status, paused, nameservers, activation date). It also distinguishes the source of truth from the Porkbun queue row, so an agent can tell it apart from get_cloudflare_queue and get_cloudflare_domain_status.

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?

Explains the drift scenario that motivates using this over the remembered queue row, which is clear contextual guidance. It stops short of naming the alternative tool or an explicit when-not-to-use condition, leaving that inference to the agent.

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