wp_purge_cache

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

There are no annotations, so the description carries the behavioral disclosure burden. It does disclose that confirmation is required when safe mode is enabled, which is a meaningful guardrail. However, it does not explain what 'safe mode' is, whether the purge is destructive to all cache layers, or what side effects to expect, leaving some behavioral uncertainty.

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 short, front-loaded sentences convey the tool's purpose, scope, and the key invocation constraint. There is no filler or redundant elaboration; every phrase 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?

For a simple single-parameter cache purge tool with no output schema, the description provides the core information needed to invoke it. The only notable gap is the undefined 'safe mode' term, which may be ambiguous without further context, but overall the tool is adequately described.

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 schema already documents the 'confirm' parameter. The description adds the exact required value ('confirm:true'), which goes slightly beyond the schema's 'Required when safe mode is enabled' by clarifying that the boolean must be true rather than merely present.

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 action ('Purge') and resource ('site cache'), and it enumerates the supported cache plugins (LiteSpeed, WP Rocket, W3TC, etc.). This is specific enough for an agent to distinguish it from the sibling tools, none of which are cache-purge operations.

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 implies when to use the tool: whenever the site cache needs clearing. It does not explicitly name alternatives or exclusion conditions, but the safe-mode confirmation requirement provides some contextual guidance for invocation. It would be stronger if it said 'use when cache must be invalidated' or listed cases where a full purge is not appropriate.

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