Get Cloudflare Records

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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered. The description adds real behavioral context beyond that: the returned fields (proxied state, proxiable flag) and a specific error condition (ZONE_NOT_READY when the zone does not exist). Not fully exhaustive, but meaningfully additive.

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 tight sentences, front-loaded with the core action and result shape, with the sibling-disambiguation and error case following. No wasted text.

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, but the description compensates by naming the key returned attributes (proxied, proxiable) and the failure mode. Adequate for a single-param read tool, though return-shape detail is only partial.

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% with a single well-described 'domain' parameter, so the schema does the heavy lifting. The description adds nothing about the parameter's format or constraints, so baseline 3 applies.

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+resource (list a domain's LIVE DNS records) with scope qualifiers, and explicitly distinguishes itself from the sibling list_dns_records by naming which zone each reads. An agent can select correctly without opening either 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 explicit when-to-use ('Once a domain has moved to Cloudflare THIS is the authoritative record set') and names the alternative (list_dns_records reads the Porkbun zone, no longer answering queries). The selection condition is unambiguous.

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