wordpress_advanced_system_clear_all_caches

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

With no annotations provided, description carries full burden. It discloses what gets destroyed (object cache, transients, opcache) and safety profile ('Safe to run anytime'). However, lacks details on required permissions, return values, or behavior when opcache is unavailable.

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 with efficient front-loading. The '[UNIFIED]' prefix appears to be metadata noise, but the core description wastes no words on tautology.

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 mutation tool with no annotations, no output schema, and completely undocumented parameters, the description is insufficient. While it explains the action, it omits necessary invocation context (parameter semantics) and response behavior.

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 0% for the single required 'site' parameter. Description fails to compensate by not mentioning the parameter at all, leaving critical invocation detail undocumented (what format site identifier takes, what it represents).

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?

Clear verb 'Clear' with specific resource 'all caches' and explicit scope (object cache, transients, opcache). Distinguishes from sibling tools like wordpress_wp_cache_flush and wordpress_wp_transient_delete_all by specifying comprehensive cache clearing.

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?

Provides safety guidance ('Safe to run anytime'), implying non-destructive operation on persistent data. However, lacks explicit guidance on when to choose this over alternatives like wordpress_wp_cache_flush or wordpress_wp_transient_delete_all.

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