Amazon Reviews API

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It only says 'Scrape' without indicating whether it is read-only, any rate limits, anti-bot risks, or output format. It does not disclose behavioral traits beyond the literal act of scraping.

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, front-loaded sentence that directly states the tool's purpose and key input. Every word contributes meaning with no redundancy or filler.

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 and no annotations, the description should provide more context about the response structure, pagination behavior, or error conditions. It mentions the high-level outputs (reviews, ratings, reviewer details) but lacks details on how many reviews per page, sort order, or what data fields to expect.

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?

All parameters (asin, page, domain, country) have descriptions in the schema, giving 100% coverage. The description adds no additional parameter semantics; it only reiterates the ASIN requirement already present in the schema.

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 uses the specific verb 'Scrape' with a clear resource ('customer reviews, ratings and reviewer details') and a clear identifier ('by ASIN'). This distinguishes it from sibling tools like amazon_search (search) and amazon_product (product details).

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 implies the tool is for when you have an ASIN and want reviews for that specific product. It does not explicitly mention when not to use it or provide alternatives, but the 'by ASIN' constraint gives clear context for usage.

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