wordpress_cache_purge

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

With no annotations, description fully discloses behavior: auto-detects active cache plugins, calls each purge API, always flushes object cache, and requires manage_options capability. This is comprehensive for a mutation tool.

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?

Description is three sentences, efficiently conveying purpose, mechanism, and requirement. No redundant information, and key detail is front-loaded.

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 single-parameter tool with no output schema, the description is complete: it explains the function, supported plugins, the flush action, the requirement, and the site parameter context. No gaps remain.

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?

Only one parameter 'site' with no schema description. The description mentions the site context but does not detail the parameter format, leaving ambiguity. Given 0% schema coverage, more explicit param guidance would improve this score.

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 clearly states the tool purges all caches on a WordPress site via the airano-mcp-bridge plugin. It lists specific supported cache plugins, making the purpose precise and distinguishable from sibling tools.

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?

Description explicitly states the tool is for purging caches. It does not provide explicit alternatives or when not to use, but the sibling list shows no other cache purge tool, and the context suggests it's the go-to for cache clearing.

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