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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely useful context: authentication is local WordPress auth and no WooCommerce REST API keys are required, which matters for call setup. It does not describe pagination defaults, ordering, or what is returned when a product has no reviews.

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 purpose before the implementation/auth detail. The 'mirrors woocommerce-mcp-server method get_product_reviews' clause is the least load-bearing part but is not enough to call the text bloated.

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 read-only paged list tool with a fully documented schema and clear annotations, the description covers purpose, scope, and auth requirements adequately. The one residual gap is that the nested `filters` bag accepts arbitrary WooCommerce REST filter keys with no illustration of which keys are valid.

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%, including the important site_id warning to call list_sites first, so the baseline is 3. The description only reinforces productId scoping and adds nothing about the nested 'filters' object, whose accepted keys remain undefined in both description and schema despite additionalProperties being true.

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?

States a specific verb and resource ('Retrieves WooCommerce product reviews') plus a scope qualifier ('optionally scoped to one product'), so an agent knows it returns a collection, not a single record. It does not explicitly name the closest sibling, wc_get_product_review (singular), so differentiation is left implicit rather than stated.

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 optional-scoping phrasing and the schema note about falling back to the global endpoint imply when to pass productId versus omit it. There is no explicit guidance on when to choose this tool over the singular wc_get_product_review sibling, and no prerequisites or exclusions are stated.

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