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

Annotations already cover the safe-read profile (readOnlyHint, openWorldHint). The description adds real behavioral context the annotations don't: the data is a sample from the product page's structured data, not a paginated feed, and no-review products return a well-formed empty result rather than an error.

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 sentences with the core purpose and returned fields front-loaded. The final two sentences (sample-vs-feed caveat, empty result) are informative but slightly repetitive in emphasizing 'sample', leaving a small amount of trimming available.

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?

An output schema exists, so return values need no elaboration, and the description still covers everything an agent needs: the input source for handle, the limited/sampled nature of the data, and the empty-result case. Nothing material is missing.

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 coverage is 100% and there is only one parameter, so baseline is 3. The description adds cross-tool meaning by specifying that handle mirrors quince_product's accepted value and the schema note points to products[].handle in search results, which is more than the schema field itself conveys.

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 (returns a product's reviews) and enumerates the returned fields (author, date, rating, review body) plus aggregate rating/count. It explicitly distinguishes itself from a full paginated review feed, which differentiates it from siblings like quince_product and the *_reviews tools of other brands.

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?

Tells the agent that handle is the same value quince_product accepts, linking the two calls, and warns that the result is a page-carried sample rather than full history. It stops short of naming an explicit alternative for agents who need the complete review set, so 4 rather than 5.

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