Purge Cache

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It names a destructive operation ('Purge') but does not explain that purge_everything overrides urls, destroys the entire zone cache, or requires CF_ALLOW_DESTRUCTIVE=true. The schema hints at these, but the description itself adds no behavioral context beyond the verb.

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?

One short sentence with zero wasted words. The purpose is front-loaded and immediately 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?

The tool has meaningful branching behavior (urls vs purge_everything, with an override and a safety requirement). The description alone doesn't help an agent choose between modes or understand the destructive scope. An output schema exists, but the description is too sparse to be contextually complete for a mutation tool with no annotations.

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%, with each parameter (zone_id, urls, purge_everything) documented inline. The description adds no parameter meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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 states the specific verb 'Purge' and the resource 'Cloudflare cache for a zone.' This clearly distinguishes the tool from zone/DNS/page-rule siblings, but it doesn't capture the two purge modes (specific URLs vs entire zone), so it's clear but slightly generic.

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 provides no guidance on when to purge specific URLs versus the entire zone, nor does it mention alternatives or exclusions. Given there are no sibling cache tools, the main usage decision is between the two modes, and no hints are given.

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