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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses pagination ('Paginated fetch'), the filtering dimensions, and enumerates the returned per-review fields plus aggregate rating histogram. It does not mention rate limits, authentication needs, or error behavior, but for a read-only GET tool the disclosed behavior is substantial and useful.

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 efficient and front-loaded: the first sentence states the action, the next sentence lists filters, then outputs, then use cases. The use-case enumeration is slightly longer than strictly necessary but earns its place for agent selection. No redundancy or tautology.

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 10 parameters, the description compensates well by enumerating both the filter capabilities and the exact return fields, including the aggregate histogram. It lacks explicit default values for page, sortBy, or mediaType and does not describe response pagination metadata, but these are minor gaps given the rich input/output description present.

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%, so the baseline is 3. The description adds value beyond the schema by clarifying the semantics of several enum-based filters: 'star rating (1-5, positive, critical)' maps to stars, 'current-variant vs all-formats' clarifies format, and 'media-only reviews' clarifies mediaType. This helps an agent choose parameter values without needing to infer from enum names alone.

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 opens with a specific verb and resource ('Get Amazon Product Reviews') and immediately expands to 'Paginated fetch of customer reviews for an Amazon ASIN,' clearly distinguishing it from the sibling tools that handle product details, search, and seller data. The scope is unmistakable even without opening the schema.

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 provides clear usage context by listing concrete use cases: voice-of-customer analysis, sentiment extraction, feature-request mining, competitor benchmarking, and review summarization. It does not explicitly exclude alternatives like getProductDetails or search_getSearchResults, but the distinct resource type makes the intended use obvious, so it earns a 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.