amazon_reviews: GET /

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

No annotations are provided, and the description only mentions 'Paginated fetch' without detailing rate limits, authentication needs, or error behavior. It does not disclose what happens on API limits or missing data, leaving gaps for an agent.

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 two sentences: a clear introductory line and a concise second sentence that packs the features and use cases. No redundant text, but could be more structured with bullet points for readability.

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?

The description lists return fields (title, body, rating, etc.) which partially compensates for missing output schema. However, given the tool's complexity (10 parameters, pagination), it lacks details on pagination limits, default page size, or error scenarios.

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% with parameter descriptions, so the baseline is 3. The description enumerates filter options (star rating, reviewer type, etc.) but does not add meaning beyond the schema. For instance, 'positive' and 'critical' stars are not explained.

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 'Get Amazon Product Reviews' and specifies the action (paginated fetch) and resource (Amazon ASIN). It distinguishes itself from sibling tools by focusing specifically on product reviews.

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 lists several use cases (voice-of-customer analysis, sentiment extraction, etc.) but does not explicitly state when NOT to use this tool or compare it to siblings like getProductDetails or search. It gives context but lacks exclusions.

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