wp_clear_cache

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It transparently lists what will be cleared, indicating a mutating/destructive operation, but does not mention prerequisites like admin credentials or potential side effects such as temporary performance impact. The enumeration of affected caches adds value but leaves some behavioral gaps.

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 a single, information-dense sentence listing all affected cache types without redundancy or unnecessary words. Every element earns its place, maximizing clarity in minimal space.

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 one-parameter tool with no output schema, the description thoroughly explains what the tool does and which caches are affected. It lacks mention of side effects or post-condition, but for basic selection and invocation, the scope of behavior is well covered.

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%—the only parameter, site_id, is already described as 'WP Engine environment name' in the schema. The description adds no additional parameter meaning, so it meets the baseline but does not exceed it.

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 uses specific verb 'Clear' with resource 'all caches on a WordPress site' and enumerates cache types (WP object cache, transients, WP Rocket, Elementor, Beaver Builder, WP Engine), distinguishing it clearly from sibling tools like wp_rocket_fix or cloudflare_fix. This is specific and unambiguous.

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 clearly implies this is the comprehensive cache clearing tool by listing all cache types, providing strong context for when to use it. It does not explicitly name alternatives or exclusions, but the scope of 'all caches' guides selection appropriately.

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