List Zones

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

With no annotations, the description carries the burden of behavioral disclosure. It clearly signals a non-mutating, account-wide list operation, which is useful. However, it does not mention pagination, rate limits, authentication, or what happens when many zones exist, so it is adequate but not rich.

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?

A single sentence delivers the core verb, resource, and scope with no filler or redundancy. The description is appropriately sized for a tool with one optional parameter and a simple list operation.

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 low-complexity tool with one well-described optional parameter and an output schema, the description supplies the essential type and scope. It lacks pagination context or sibling-routing guidance, but those are minor gaps for a basic read-only list operation.

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?

The single optional parameter name_filter is fully documented in the input schema with its own description, so schema coverage is 100%. The tool description adds nothing about the filter, but the schema already provides the necessary meaning, so the baseline of 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?

The description states a specific verb ('List'), a clear resource ('Cloudflare zones'), and an account-level scope ('on this account'). 'All' implies a collection operation that loosely distinguishes it from get_zone, but it does not explicitly name or contrast any sibling tool.

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?

No guidance is given about when to use this tool versus list_dns_records, get_zone, or get_zone_settings. There are no exclusions, conditions, or references to alternatives. The phrase 'when you need all zones' is implied but essentially tautological.

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