Returns one crawled Goodreads book record by id from dataset id enum value goodreads-books. Use datasets_goodreads_books_search to search Goodreads books dataset.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Goodreads book id, e.g. 2767052. |
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | The tool result payload (shape varies per tool; see each tool's docs resource). |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=true and openWorldHint=true, so safety and the external-scraped nature are covered. The description adds that the record is 'crawled' from the goodreads-books dataset, but does not describe pagination, availability, or result completeness beyond that.
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 short sentences, front-loaded with the operation and followed immediately by the alternative, with zero redundant text.
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?
An output schema exists, so return values need not be explained here. For a single-param lookup tool with annotations and a search sibling named, the description is nearly complete; minor operational details (rate limits, missing-id behavior) are absent.
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 100% and the schema provides a clear example id ('2767052'), so parameter semantics are already handled. The description adds no format or syntax detail beyond what the schema document provides.
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?
States the specific verb 'Returns' and the resource 'one crawled Goodreads book record', including the dataset enum value. It is clearly distinguishable from sibling datasets_goodreads_books_search, which is named as the alternative.
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?
Explicitly names the sibling search tool and states the condition for using it ('Use ... to search'), leaving no ambiguity about when to use retrieval-by-id versus search.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
