cloudflare_cache_purge

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

With no annotations, description adds a key behavioral trait: purge_everything causes a temporary origin load spike. However, it omits other details like propagation delay, rate limits, or required permissions, leaving gaps.

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 sentences: first lists purge modes, second provides a critical caution. No unnecessary words, front-loaded with the main action. Highly efficient.

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?

Covers the core purge functionality and the key risk (load spike). Lacks information about output/return values, propagation time, or error states, but for a purge tool with good schema descriptions, it is mostly complete.

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 coverage is 100% with parameter descriptions. Description adds minimal extra meaning beyond listing purge modes and the caution for purge_everything. Baseline 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?

Clearly states verb 'Purge' and resource 'cached files from Cloudflare's edge', listing four specific purge modes: URLs, tags, prefixes, or everything. This distinguishes it from sibling tools that focus on DNS, zones, WAF, etc.

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?

Explicitly warns about the origin load spike from purge_everything, but does not guide when to choose files vs tags vs prefixes. Since no sibling tools are for cache, it implicitly covers the main use case, but could be clearer on mode selection.

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