Cloudflare purge

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

Annotations already mark the tool as destructive (destructiveHint=true), so the description adds little. 'Prompts.' could imply a confirmation step, but it is vague and unexplained. No additional behavioral context such as impact on cache or reversibility is provided.

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 short but not effective. The second sentence 'Prompts.' is unclear and appears to be a placeholder or incomplete thought. It does not earn its place and detracts from clarity.

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 destructive tool with one parameter and no parameter explanation, the description is inadequate. It does not mention required inputs, effects, or any cautions. The presence of an output schema does not compensate for missing parameter and usage details.

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%, so the description must explain the 'zone' parameter. It does not indicate whether a zone ID or name is expected, or any format. The single parameter remains completely undocumented.

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 phrase 'Purge a zone cache' clearly identifies the action and resource. It is distinct from sibling Cloudflare tools like cloudflare_dns or cloudflare_zones, though it does not explicitly name alternatives.

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?

No guidance is given on when to use this tool or when to prefer a sibling. The cryptic 'Prompts.' adds no context. There is no mention of prerequisites like obtaining the zone ID.

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