cloudflare_zones

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

No annotations are provided, so the description carries the full behavioral burden. It discloses only the 'permitted' scope, implying an access restriction, but says nothing about rate limits, pagination termination, ordering, or what a page contains — all relevant for a paginated listing 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?

A single tight sentence with the verb, resource, and scope front-loaded and no filler. The semicolon clause about pagination is useful, though the phrasing is slightly clipped.

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 optional-parameter listing tool with no output schema, the description covers the core purpose but leaves the agent guessing about default paging behavior and whether pagination metadata is returned. It is the minimum viable level of completeness rather than fully adequate.

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?

With one parameter and 0% schema description coverage, the description must compensate; it does identify that 'page' is the pagination control, which the schema (integer, min 1) does not state. However, it omits the default page and page size semantics, so the compensation is only partial.

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 permitted Cloudflare zones') plus the access scope ('permitted'), which is enough to distinguish it from mutation siblings like cloudflare_upsert and cloudflare_delete. It stops short of naming how it differs from cloudflare_records, so it is clear but not sibling-differentiated.

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?

There is no explicit when-to-use or when-not-to-use guidance. The description never mentions the alternative cloudflare_records (for DNS records within zones) or any prerequisite for listing zones, leaving the agent to infer selection from the tool name alone.

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