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

Annotations already cover read-only/idempotent/non-destructive/closed-world, yet the description adds real behavioral value: pagination, excluded data classes, the untrusted-data warning about comment content, and the fact that counts include repeat purchases rather than unique buyers. It stops short of mentioning auth needs, rate limits, or cursor expiry behavior.

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?

Four short sentences, zero filler, with the core purpose and output shape front-loaded before caveats. Each sentence carries distinct information (scope, exclusions, safety, counting semantics).

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, the description does some of the return-value work (reviews plus separate aggregates, count semantics) but omits result fields, pagination mechanics, and the meaning of the status/version filters. Adequate but clearly incomplete for a five-parameter read 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 0% across five parameters, and the description names none of them. The status enum values (active/validation/retired/all) and the version pattern are left entirely unexplained, so the description does not compensate for the coverage gap; only 'paginated' loosely gestures at limit/cursor.

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+resource (read public reviews) plus the secondary output (separate rating aggregates) for a product. An agent can distinguish it from get_review (single review) and list_review_replies (replies) without opening the schema.

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 exclusion of private feedback and tests implies when this tool is appropriate versus other review surfaces, but it never names an alternative sibling or states an explicit when-not condition. Usage is inferable rather than directed.

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