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

Annotations already declare destructiveHint=true, readOnlyHint=false, openWorldHint=true and idempotentHint=false, so the safety profile is covered. The description adds real context beyond that: an explicit human-confirmation workflow tied to the confirm flag, and the authentication model (local WordPress auth, no WooCommerce REST API keys). It does not state what exactly is lost or altered by an update, which keeps it from a 5.

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?

Three short sentences, front-loaded with the action, then the safety workflow, then the auth model. Nothing is padded, though the 'Mirrors woocommerce-mcp-server method update_product_review' clause is implementation trivia that does not help an agent decide or call correctly.

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 destructive mutation with a nested free-form reviewData object (empty properties, additionalProperties=true), the definition leaves the most consequential detail unspecified: which review fields can actually be updated. No output schema exists, so return behavior need not be explained, but the reviewData gap is a meaningful omission for a destructive tool.

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 the schema already explains site_id, reviewId, confirm, productId and reviewData; the baseline of 3 applies. The description's note about confirm=true only after user confirmation restates what the schema field already says, and it adds no detail about which review fields the reviewData object accepts.

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 and resource: 'Updates a WooCommerce product review.' That is unambiguous and clearly separable from wc_create_product_review and wc_delete_product_review by the verb alone. It stops short of an explicit sibling differentiation, so it lands at 4 rather than 5.

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?

It gives one concrete usage precondition – 'Ask the user for confirmation before calling with confirm=true' – which is genuine workflow guidance. However, it never says when to choose this over adjacent mutation tools such as wc_update_product or wc_update_product_meta, and offers no when-not-to-use condition beyond the confirmation gate.

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