Cloudflare zones

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description does not need to restate that it is a read-only operation. It adds a practical note that a token is required, which is useful behavioral context. However, it does not describe what happens if the token is missing or invalid, nor any pagination or error behavior. With annotations covering the safety profile, the added token requirement justifies a 3.

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 extremely concise: two short sentences that immediately state the purpose and a key requirement. There is no filler, and the core action is front-loaded. Every word adds value, making it an ideal model of efficiency.

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 tool is simple (one optional parameter, no required fields) and has an output schema, so the description need not detail return formats. However, the 'name' parameter is completely unexplained, and the token requirement lacks specifics (e.g., how to provide it or error behavior). These gaps prevent the description from being fully complete, though the overall simplicity keeps it from being inadequate.

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 schema description coverage is 0%, so the description must compensate for parameter clarity. The schema has a single optional 'name' parameter with a default, but the description never mentions it. The agent is left without any explanation of what 'name' does—whether it filters zones, acts as an exact match, or something else. This is a significant gap given the schema provides no descriptions, and the description does not address the parameter at all.

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 clearly states the action ('List zones') and identifies the resource (zones) along with the returned fields (id, name, status, plan). It differentiates from sibling tools like cloudflare_dns or cloudflare_purge, which focus on other Cloudflare operations. The verb and resource are specific, leaving no ambiguity about what the tool does.

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 is used to list zones, but it does not explicitly state when to use it versus alternatives or when not to use it. It mentions a prerequisite ('Needs token') but no exclusions or alternative tools are referenced. The guidance is implied rather than explicit, so it meets the threshold for a 3 but lacks direct routing to or away from other tools.

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