wordpress_wp_cache_flush

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

No annotations are provided, so the description carries the burden. It states the tool is safe to run anytime, implying non-destructive behavior, but does not disclose potential performance impacts, authentication needs, or what happens to cached data beyond being cleared.

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 concise sentence without unnecessary words. However, the '[UNIFIED]' prefix is unclear and could be omitted or explained.

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 the single undocumented parameter and lack of differentiation from sibling tools, the description is incomplete. It fails to provide adequate context for correct tool invocation.

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?

The schema has 0% description coverage for the required 'site' parameter, and the description does not explain what 'site' refers to (e.g., ID, URL, name). The agent receives no guidance on how to populate this parameter.

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 states 'Flush WordPress object cache' and specifies the cache types (Redis, Memcached, file cache), making the purpose clear. However, it does not distinguish from similar siblings like wordpress_cache_purge, so differentiation is lacking.

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 mentions 'Safe to run anytime,' which gives some usage guidance. But it provides no context on when to use this tool over alternatives (e.g., wordpress_cache_purge, wordpress_transient_flush) or any prerequisites.

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