product_reviews

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

With no annotations provided, the description carries the full burden. It does disclose the authentication requirement (logged in user cookie) and the pagination limit (10 reviews/page), which are useful behavioral traits. However, it doesn't disclose rate limits, throttling, response shape, or whether the operation has side effects on the account.

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?

The description is a single concise sentence that is front-loaded with the core purpose. It's efficient and free of filler, though it could perhaps mention more about output without becoming verbose.

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 tool with 11 parameters and no output schema, the description is minimal. It covers the essential purpose and pagination but doesn't help an agent understand the returned structure, the authentication setup requirements (how the cookie is managed), or whether the three 'Example value:' parameters are boolean flags. Given the parameter complexity, more context would help.

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 documents all 11 parameters. However, the description itself adds context by noting pagination behavior and the logged-in requirement that relates to how the tool functions. Three parameters (current_format_only, images_or_videos_only, verified_purchases_only) have only 'Example value:' placeholder descriptions, making the system's schema coverage effectively partial despite the 100% claim output.

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 clearly states the tool gets and paginates product reviews for a given ASIN using an authenticated user cookie. It distinguishes from sibling tools like product_review_details (which handles single review details) and seller_reviews (seller-focused), though it doesn't explicitly call out these distinctions.

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 description mentions pagination (up to 10 reviews per page) and the login requirement (user cookie string), giving practical usage context. However, it doesn't explicitly state when to use this vs alternatives like product_review_details or when not to use it, though the sibling separation is reasonably clear from names alone.

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