cf_purge_cache

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

With no annotations provided, the description carries the full behavioral disclosure burden. It states that cache is purged, which signals a state-changing operation, but it does not mention whether the purge is irreversible, whether purgeEverything and selective purging are mutually exclusive, or what the impact is on cached content. This is a material gap for a destructive operation.

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 a single front-loaded sentence with no wasted words. It is concise and readable, though it sacrifices useful detail; the brevity is a strength structurally but contributes to the incompleteness already penalized.

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?

This is a state-changing operation with no annotations, no output schema, and low parameter documentation. The description covers only the high-level action and scope, leaving out parameter relationships, expected return values, and operational constraints, so it is not complete enough for an agent to invoke reliably.

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 only 17%, with zoneId being the only documented parameter. The description adds nothing about tags, files, hosts, prefixes, or purgeEverything, and fails to explain the selective-versus-full purge relationship. An agent cannot determine the semantics of five of the six parameters from the description or the schema.

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 uses a specific action verb ('Purges') with a clear resource ('Cloudflare cache') and scope ('for a zone'). It is unambiguous about what the tool does, but it does not explicitly distinguish itself from sibling cache-related tools like cache_stats or cf_get_analytics.

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 about when to use this tool rather than an alternative, when not to use it, or prerequisites such as zone ownership. The only implied context is that it is for purging cache, which is not enough to help an agent choose among the many sibling tools.

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