purge_cache

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

No annotations are provided, so the description must disclose behavioral traits on its own. It only states 'Clear CDN cache' without mentioning whether the action is irreversible, how long it takes, any permission requirements, or side effects. This is a significant gap for a destructive operation, leaving the agent without critical operational context.

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 extremely concise, using two short sentences and an example. It front-loads the core purpose and provides immediate clarity without any redundant information. Every word earns its place.

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?

Given the simplicity of the tool (2 parameters, no nested objects), the description is largely adequate for basic invocation. However, it lacks behavioral details (e.g., irreversibility, timing) and does not explain return values, which is important since there is no output schema. It is functional but not fully complete.

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 parameters `site_id` and `urls` are already fully documented in the schema. The description's phrase 'Purge everything or specific URLs' aligns with the `urls` parameter but does not add new meaning beyond what the schema already states. Baseline 3 is appropriate.

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's function: 'Clear CDN cache for a website.' It specifies the resource (CDN cache) and the action (clear/purge), and distinguishes it from sibling tools like delete_website or publish_site. The example reinforces the purpose, making it obvious what the tool does.

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 clear usage context: 'Purge everything or specific URLs.' It implies the tool is used when a website's cache needs to be cleared, with an option to target specific URLs. However, it does not explicitly mention when not to use it or alternatives, so it stops short of full guidance.

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