List Zones

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

The readOnlyHint annotation already indicates this is a safe read operation. The description adds that it returns zone IDs needed for other operations, which is useful downstream context, but it does not disclose additional behavioral traits such as pagination behavior or response structure beyond what the schema implies.

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?

The description is three short, purposeful sentences: purpose, filters, and output utility. Every sentence earns its place, with no filler or redundancy.

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 simple list operation, the description covers the core purpose, optional filters, and the key return value (zone IDs). The schema provides full parameter details including enums and defaults, and the readOnly annotation covers safety, making this description complete enough for an agent to invoke 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%, so the baseline is 3. The description only rephrases the name and status filters without adding new meaning or details beyond the schema's parameter descriptions.

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 'List all DNS zones in the Cloudflare account' with a specific verb and resource, clearly indicating a list operation with optional filters. This distinguishes it from sibling tools like get_zone (single zone) and list_dns_records (records within a zone), even without explicit exclusions.

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?

The description provides clear context: it returns zone IDs needed for other operations, implying when to use this tool. It also mentions optional filtering by domain name or status. However, it does not explicitly state when to use alternatives like get_zone, so it lacks exclusions.

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