cf_get_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, and it does convey that this is a read-only listing operation scoped to the authenticated user. However, it does not mention pagination behavior, default per-page values, rate-limit implications, or what fields the returned zones contain.

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, front-loaded sentence with no filler. It states the core action and scope efficiently.

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 tool with no annotations, no output schema, and no parameter descriptions, this description is too thin. It does not explain what a returned zone looks like, how filtering or pagination works in practice, or how this list might feed into later Cloudflare operations. An agent can invoke it, but not confidently reason about its 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 0%, and the tool description provides no explanation of the 'name', 'page', 'status', or 'perPage' parameters. The schema only gives types/enums, so the agent receives no semantic guidance beyond raw parameter names.

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 names a specific verb ('Lists'), a precise resource ('Cloudflare zones'), and a scope ('accessible to the authenticated user'). It is immediately distinguishable from sibling Cloudflare tools like cf_list_dns_records or cf_purge_cache.

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 guidance about when to use this tool versus alternatives, no suggested workflow, and no mention of sibling tools that might serve related purposes. The intended use is implied but never stated.

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