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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is largely covered by structured data. The description contributes the confirmation gate and the categories of cache affected, but it does not say what state is lost or what breaks (e.g. whether uncached pages or sessions are temporarily affected).

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 with no filler; the operation and scope come first and the safety requirement follows. Nothing in the text is wasteful, though there is no further structure such as a precondition or expected effect.

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 two-parameter, fully documented destructive tool with annotations covering the safety profile, the definition is minimally adequate: purpose and the confirmation gate are clear. It omits when to select this over the more surgical transient-clearing siblings, which is the main remaining gap an agent would face.

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 parameters are already documented, including the instruction to call list_sites first and not to pass a URL or post ID. The description only restates the confirm=true condition already present in the schema, adding no new parameter meaning.

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 a specific verb ('Clear') and a specific resource with scope ('WooCommerce product, order, shipping and related transient caches'), so an agent can tell what the tool does without opening the schema. It stops short of naming how it differs from the closest sibling, wc_maint_clear_expired_transients, whose scope is presumably narrower.

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 gives one concrete procedural rule - obtain explicit user confirmation and only then pass confirm=true - which is real usage guidance. It does not state when this broad cache clear should be preferred over targeted siblings such as wc_maint_clear_expired_transients or wp_clear_cache, leaving the agent to infer the choice from tool names.

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