Retrieve a Goodreads book by ID for its description, authors, series, genres, format, pages, publisher, publication date, ISBNs, and 1-5 star rating distribution.
Get a Goodreads book. Returns a Goodreads book: description, authors, series, genres, format, pages, publisher, publication date, ISBNs, and aggregate rating with the full 1-5 star distribution.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Goodreads book id |
Changes observed during successful MCP inspections.
v1.5.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. 'Get' and 'Returns' imply a read-only operation and the return fields are listed, but there is no disclosure about permissions, error handling, or whether the operation has any side effects.
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 action and then the return payload. Every clause serves to specify what the tool returns, with no filler.
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?
For a simple one-parameter retrieval tool with no output schema, the description adequately specifies the return contents. The main missing context is usage guidance versus siblings, but the parameter and return shape are sufficiently covered.
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 single 'id' parameter is documented as 'Goodreads book id'. The description adds no further parameter semantics, so the baseline of 3 is appropriate.
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 a specific verb ('Get') and resource ('Goodreads book'), and enumerates the returned fields. It does not explicitly differentiate from sibling tools like goodreads_search or goodreads_book_reviews, but the fetch-by-id purpose is clear.
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?
No when-to-use guidance is provided, and no alternatives such as goodreads_search or goodreads_book_reviews are named. The agent must infer that this tool is for retrieving a known book ID rather than for searching or browsing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.