list_zones

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The verb 'List' signals a read operation and the scope is stated, but there is no mention of pagination, response shape, or that 'all zones' may require iterating over pages. This is a meaningful gap for a list endpoint with page and per_page parameters.

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 a single front-loaded sentence with no wasted words. It conveys the core action, resource, and scope efficiently and is appropriately sized for 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?

The schema richly documents parameters, but with no output schema and no annotations, the description should at least hint at pagination or response characteristics. 'List all zones' is minimally viable, yet an agent could reasonably wonder whether one call returns everything or whether it must page through results.

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 schema already documents all five parameters with helpful descriptions. The tool description adds only the 'domains' synonym and the account scope, which does not materially enhance parameter understanding beyond the schema.

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 uses a specific verb ('List'), a clear resource ('zones'), adds the parenthetical clarification ('domains'), and states the scope ('in the account'). This clearly distinguishes it from single-zone tools like get_zone and from other account-level list tools.

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 implies the tool's usage: call it when you need the zones belonging to the account and want them as a list. However, it does not explicitly contrast it with get_zone or mention when not to use it, leaving some routing to inference.

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