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

Annotations declare readOnlyHint=false, yet the description calls the tool 'read-only' — a direct contradiction about side-effect profile. The credit cost, refund-on-failure, and hidden-password-protected-reviews details are genuinely useful behavioral context, but the read-only claim conflicts with the structured safety signal and could mislead an agent about side effects.

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?

Five short, front-loaded sentences with no filler, and the cost/refund facts are stated plainly. It is efficient, though the opening sentence spends prime space on access mode instead of the operation.

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?

This is an aggregate/facet tool with no output schema, so the description must explain what comes back — instead it says nothing about price ranges, rating counts, stock-status counts, or the fact that unsupported fields may be null. Combined with the read-only contradiction against readOnlyHint=false, an agent has no reliable picture of behavior or results.

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 all eight parameters (keyword, categoryId, taxonomies, attributeTaxonomies, calculate* toggles) are already documented in the schema with constraints and defaults. The description adds no parameter meaning at all, so the 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 name says 'product collection data' but the description never states what the tool actually does — it only says 'Anonymous read-only official Store API data'. Nothing mentions aggregates, taxonomy counts, price ranges, rating counts, or stock-status counts, so an agent cannot tell from the description that this returns facet/aggregate data rather than products. The single specific fact (it's Store API data) restates the naming rather than clarifying the operation.

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?

'Availability depends on the store version and configuration' is a caveat, not usage guidance: it does not say when to choose this tool or which sibling to use instead (e.g., nexscope_woocommerce_products for actual product listings vs. this for counts). No prerequisites or exclusion conditions are given beyond the auth note.

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