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

Annotations already indicate destructiveHint=true (destructive operation). Description adds the constraint of max 30 URLs and 'forces CDN to fetch fresh content', but does not elaborate on required permissions or irreversible effects. The description does not contradict annotations.

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?

Extremely concise single-sentence description with an action prefix. No filler; every word adds value. Front-loaded with key information.

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 simple 3-parameter tool with output schema, description covers core behavior. Missing mention that purge_everything and files are likely mutually exclusive (not stated). Otherwise adequate for the operation.

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% with all parameters described. Description summarizes options but adds no new depth. Baseline 3 is appropriate as the schema already provides sufficient detail.

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?

Description clearly states the action (purge), resource (Cloudflare CDN cache), and scope (all or specific URLs up to 30). It distinguishes from sibling tools like DNS operations and zone listing by specifying cache purging.

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?

Description implies when to use (refresh cached content) but does not provide explicit when-not-to-use or mention alternatives. Given no sibling cache tool, usage is relatively clear but lacks exclusions.

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