bunny_purge_url

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

The annotations include destructiveHint=false, indicating the tool is not destructive. The description adds context that origin files remain untouched, which clarifies that cache purging is the only effect. It also explains the wildcard behavior and the fresh-content consequence, going beyond the schema's bare parameter types.

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?

Three concise sentences front-load the core action and outcome, then a relevant usage hint and one clarifying safety note. Every sentence earns its place without extraneous detail.

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 two-parameter, no-output-schema tool, the description covers the purpose, the path-wildcard behavior, and a critical non-destructive guarantee. An agent has enough context to decide when to call it and what to pass, and the absence of return-value details is acceptable since no output schema exists.

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%, so the baseline is 3; the description earns a 4 by reinforcing the wildcard usage and clarifying that the operation affects only cache, not origin storage. The async parameter is described in the schema and not repeated in the tool description, so no extra meaning is lost.

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 the specific verb 'Purge', the resource 'a specific URL from the global CDN cache', and the expected outcome: 'the next request fetches fresh content from the origin.' The description also distinguishes this from the sibling bunny_purge_pull_zone_cache by focusing on a URL rather than a whole pull zone.

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 gives practical guidance on when to use the wildcard append for path purges and explicitly says it does not delete origin files. It does not explicitly name alternatives, but the sibling list reveals bunny_purge_pull_zone_cache as the coarser-grained alternative; the URL-level description implies this tool is for targeted URLs rather than whole-zone cache clearing.

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