cf_dns_list

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

No annotations are provided, so the description carries the full burden. It discloses output content and the zone-to-id mapping via CLOUDFLARE_ZONE_MAP, which is genuinely useful, but omits pagination behavior despite a 'limit' parameter, and says nothing about auth or rate limits.

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 tightly written sentences with the core action front-loaded and zero filler. Every clause adds 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?

An output schema exists so return values need not be described, and the description nonetheless adds the zone-mapping detail. The only real gap for a list tool is the undocumented limit/pagination parameter.

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 0%, so the description must compensate. It explains the zone parameter can be a domain or an id in CLOUDFLARE_ZONE_MAP and covers type/name as filters, adding real meaning beyond the bare schema, but 'limit' (default 100) is entirely undocumented.

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 DNS records of a zone') and names the return fields (content, TTL, proxy status). This clearly contrasts with the cf_dns_upsert sibling, though it never explicitly names the alternative it is not.

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?

Notes that type/name are optional filters, which implies some usage, but gives no explicit when-to-use, when-not-to-use, or alternative (e.g., cf_dns_upsert) guidance. The agent must infer the context.

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