Cloudflare: List dns records

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

readOnlyHint=true already declares the safety profile, so the annotation bar is met. The description adds genuine value by enumerating returned fields (id, type, name, content, TTL, proxied, comment) and noting pagination, but gives no rate-limit, default page size, or ordering behavior.

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, front-loaded with purpose and then return shape, with no filler. The only mild inefficiency is that the return-field list is a clause rather than an independent, optional detail.

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 read-only list tool with no output schema, disclosing returned fields is a real contribution. However, the absence of any explanation for the two required parameters and the pagination controls leaves meaningful gaps for a 7-parameter tool.

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 0%, so the description must carry all parameter meaning. It names three filter parameters (type, name, content) and gestures at pagination, but says nothing about the required site and zone_id distinction or how page vs. per_page behave, leaving 4 of 7 parameters undocumented anywhere.

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?

The description states a specific verb and resource ("List DNS records for a zone") plus scope via filters, which clearly separates it from the get/create/update/delete DNS siblings. It stops short of naming an explicit alternative, but the intent is unambiguous.

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 implied by 'List ... with optional filters', telling the agent this is the enumeration path with filtering. There is no explicit when-to-use vs. cloudflare_get_dns_record or when to prefer server-side filtering over client-side, so guidance stays at inference level.

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