Purge entire Cloudflare zone cache

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety bar is low, but the description still earns credit for disclosing a real operational consequence the annotations cannot convey: the origin is hit by all traffic immediately and must be able to absorb it. It does not mention propagation delay or whether the purge is scoped to the whole zone only.

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?

Two short sentences, front-loaded with the action and followed by the consequence. The phrasing 'Every next request goes to the origin at once' is slightly awkward but carries no waste.

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?

A two-parameter tool with an output schema and full annotation coverage needs little more than an accurate statement of effect and risk, both of which are present. Nothing essential is missing, though noting the alternative selective purge would close the remaining gap.

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%, and the description adds no meaning beyond the schema for either 'zone' or 'account'. Baseline 3 applies because the schema does the work.

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 ('Purge the whole cache of a Cloudflare zone') and the word 'whole' implicitly separates it from the sibling cloudflare_zone_cache_purge. It does not name that sibling explicitly, so the differentiation is inferred rather than stated.

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 only implied: purging the entire cache is the heavy-handed option, so a targeted purge should normally be preferred, but the description never says when to choose this over cloudflare_zone_cache_purge. No prerequisites are stated either.

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