Purge CDN cache

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

The description adds useful behavioral context beyond the annotations: the automatic domain-based zone matching when resource_id is omitted, and the distinction between full-URL and resource-scoped purging. Annotations already indicate idempotent, non-destructive behavior, so the bar is lower, but this description still contributes meaningful details.

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 concise sentences efficiently pack all essential information. The structure clearly separates the two modes, making it easy to parse. Zero wasted words.

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 tool with 3 parameters and no output schema, the description fully covers the key scenarios and edge cases (resource_id vs no resource_id, clear_all vs specific URLs). It is complete for an agent to understand and invoke the tool correctly.

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%, so the baseline is 3. The description enhances parameter understanding by explaining the interplay between resource_id, clear_all, and urls: how resource_id changes the scope and meaning of the other parameters. This adds value beyond the individual field descriptions.

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 clearly states the tool purges cached content, using a specific verb+resource structure. It also distinguishes the two primary usage modes (with and without resource_id), which differentiates it from sibling tools like warmup_cache (which pre-loads rather than purges).

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 provides explicit guidance on when to use each mode: with resource_id for resource-scoped purges (all or specific URLs), and without resource_id for URL-based purges across all resources. It does not explicitly name alternatives like warmup_cache for the inverse operation, but the usage context is clear.

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