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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is carried by structured data. The description adds the useful human-in-the-loop confirmation requirement, but says nothing about what actually loses state or whether templates are regenerated afterwards, which is the key unknown for a cache purge.

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 short sentences, front-loaded with the action, with no filler. The second sentence largely duplicates the schema's confirm description, a minor redundancy that keeps it from a 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?

With no output schema and a destructive, non-idempotent operation, the definition is complete enough to call safely (confirmation gate is explicit) but thin on effects — it never states what state is lost or what the tool returns, which matters for a purge operation.

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 description coverage is 100%, so both site_id (list_sites id, not a URL or post ID) and confirm are fully documented in the schema. The description only restates the confirm=true convention already present in the schema, adding no new parameter meaning; baseline 3 applies.

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 opens with a specific verb+resource ('Clear the WooCommerce template cache'), so the agent knows exactly what will be affected. It does not distinguish itself from the many nearby cache-clearing siblings (wp_clear_cache, wc_maint_clear_system_status_theme_info_cache, wc_maint_clear_transients), leaving the agent to infer scope from the name.

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?

There is procedural guidance — ask the user, then pass confirm=true — which covers the gating workflow. However, there is no guidance on when this tool is appropriate versus the other clear_cache variants, so selection among siblings remains implied rather than stated.

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