bunny_purge_pull_zone_cache

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

Annotations already cover non-read-only, non-destructive, and idempotent behavior. The description adds useful context beyond them: it does not delete origin files and forces all edge servers to refetch from origin on the next request, clarifying the exact blast radius.

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 with no filler. The primary action and scope lead the description, followed by a key non-destructive clarification and a concise pointer to the sibling tool.

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 one-parameter cache purge action, the description covers what it does, what it affects, what it does not affect, and which sibling to use for a different scope. Annotations and schema already supply the remaining operational information.

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?

The single parameter id is already fully described in the schema as 'Pull Zone ID', so schema coverage is effectively 100%. The description adds no additional parameter detail, but none is needed for this simple one-argument tool.

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 entire CDN cache for a pull zone. It clearly distinguishes itself from bunny_purge_url by noting it is for the full zone, not a single URL.

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 names the alternative bunny_purge_url and gives the decisive condition: use that tool for single-URL purges. This gives an agent clear routing guidance with no inference required.

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