wordpress_clear_cache

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

No annotations are provided, so the description carries the full burden. It does identify the exact cache targets that will be cleared, which is useful. However, it doesn't disclose whether the operation is destructive, requires authentication, or has side effects like temporary performance impact after clearing. Scored 3.

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?

One short sentence with no fluff. It front-loads the action and provides the essential specifics. Scored 5.

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 zero-parameter tool with no output schema, the description covers the core action well, naming the three cache types. It doesn't mention return values or effects, but given the simplicity, this is largely sufficient. However, a note about what happens after clearing (e.g., caches rebuild on demand) would improve completeness. Scored 4.

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 tool accepts zero parameters, and the input schema is complete. Baseline for zero-param tools is 4; the description doesn't need to add parameter semantics since there are none.

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 uses a specific verb ('Clear') and identifies the resource ('WordPress caches') with concrete subtypes (transients, object cache, page cache). This clearly distinguishes it from sibling tools like wordpress_optimize_database or wordpress_cleanup_database, which target database instead.

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 provides no when-to-use guidance, no mention of alternatives, and no exclusions. It doesn't say that this is a maintenance operation versus a fix for stale data, nor when to prefer it over database optimization or rewrite flush. Scored 2.

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