amazon_reviews: GET /

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

No annotations exist, so the description carries the full burden. It describes pagination, filters, and return fields but lacks details on rate limits, authentication, or API quotas. The read-only nature is implied, but not explicitly stated.

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, well-structured paragraph that front-loads the main purpose, then details filters and return data, and ends with use cases. It is concise but could benefit from bullet points for clarity.

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?

Given 10 parameters, 1 required, and no output schema, the description covers input filters, output fields, and use cases adequately. Missing pagination specifics (e.g., page size) but otherwise complete for a data-fetch 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 coverage is 100%, and the description adds meaning beyond enum labels (e.g., explains 'positive' and 'critical' star filters). It also lists returned fields (title, body, etc.), compensating for the lack of output 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 clearly states the tool retrieves Amazon product reviews with pagination and filters, specifying the resource (Amazon ASIN) and action (get). It distinguishes from siblings, which focus on other platforms like Airbnb, Google, etc.

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?

Explicit use cases are provided: voice-of-customer analysis, sentiment extraction, etc. While no direct alternative mentions, the context implies it's for Amazon reviews, differentiating it from sibling tools for other sources.

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