list_zones_tool

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

With no annotations, the description carries full burden. It usefully discloses token-scoped visibility and pagination bounds (max 50, default per_page), but says nothing about read-only safety, rate limits, or how pagination interacts with filters. Adequate but thin for a zero-annotation tool.

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?

Purpose is front-loaded in one sentence, then Args and Returns blocks. The Returns block partially duplicates the output schema, but the overall structure is tight and scannable.

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 the Returns note is optional rather than required, and all four parameters are covered. Combined with the front-loaded scoping, an agent has enough to invoke this correctly; only deeper auth/rate-limit behavior is absent.

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, and it does: each of the four parameters is documented, including the meaningful status enum values (active, pending, initializing, moved, deleted) and the per_page max of 50 that the bare schema lacks.

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 and resource ('List all Cloudflare zones') and scopes it to what the API token can access. It doesn't explicitly distinguish itself from the sibling get_zone_tool (singular retrieval), though the listing scope is implicit in the verb.

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 the list/collection framing and the filter parameters, but the description never says when to reach for this versus get_zone_tool or the various rule-listing siblings. No exclusions or prerequisites are given.

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