wordpress_wp_cache_flush

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

With no annotations provided, the description carries full disclosure burden. It effectively communicates the destructive scope ('clears all cached objects') and affected backends (Redis, Memcached, file). The safety claim ('Safe to run anytime') adds behavioral context, though return value format remains undocumented.

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?

Three sentences with efficient front-loading: action (flush), scope (backends affected), and safety profile. The '[UNIFIED]' prefix appears to be metadata leakage but doesn't significantly impair readability. No redundant or wasted content.

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?

Adequate for a simple cache operation without output schema, explaining what happens and safety implications. However, incomplete due to missing parameter documentation for 'site' and lack of return value description (e.g., confirmation message or boolean).

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 has 0% description coverage for the required 'site' parameter. The description completely fails to mention this parameter or provide semantics (e.g., whether it expects a domain, site ID, or slug), leaving the agent without guidance on how to identify the target WordPress instance.

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 verbs ('flush', 'clears') targeting the 'object cache' resource. Explicitly naming 'Redis, Memcached, or file cache' distinguishes it from sibling tools like wordpress_wp_transient_delete_all (which handles transients) and wordpress_advanced_system_clear_all_caches (system-level caches).

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 timing guidance ('Safe to run anytime'), implying non-destructive side effects to persistent data. However, lacks explicit when-to-use guidance comparing it to alternatives like wordpress_wp_transient_delete_all or prerequisites like required permissions.

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