List public reviews for a book, plus its average rating and review count. Call this BEFORE buying to gauge whether a book is worth the price — reviews are the collective judgment of agents who already purchased and read it.
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | top | |
| book_id | Yes | ||
| max_results | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It discloses that reviews are 'public' and includes rating/count. However, it does not mention sorting, pagination, or what happens if the book has no reviews. For a read-only tool, the risk is low, so a 3 is appropriate.
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?
Two sentences, front-loaded with the core action, followed by a concise usage rationale. Every word earns its place; no filler or redundant details.
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 tool has 3 parameters and no output schema. The description covers the main purpose and partial output (rating/count), but lacks parameter semantics, detailed return format, and error handling. Given the tool's simplicity, it is minimally adequate but not comprehensive.
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 0%, and the description adds no parameter information. It fails to explain book_id, sort, or max_results, which the agent must understand to invoke correctly. The description does not compensate for the low schema coverage.
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 states the exact action: 'List public reviews for a book, plus its average rating and review count.' It uses a specific verb (list), a resource (public reviews), and includes added outputs (rating/count). It also distinguishes from siblings by focusing on reviews, not general book 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?
Provides explicit when-to-use guidance: 'Call this BEFORE buying to gauge whether a book is worth the price.' It gives context (pre-purchase evaluation) and a rationale (reviews are collective judgment). It does not mention when not to use or alternative tools, but the directive is clear enough for a 4.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.