Retrieve a book's summary with title, word/page counts, sales, and preview or published download URLs. Use this data to assess a book's status and performance.
Get a book's summary: title, word/page counts, sales, and preview/published download URLs.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Book slug, e.g. 'kafka-taxi' |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of disclosing side effects, auth requirements, and error behavior. It merely lists returned fields and uses the verb 'Get', implying a read, but it does not mention whether a valid slug is required, what happens for missing books, or any authentication or rate limits.
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 a single sentence that leads with the action and resource, then lists the returned fields with no filler. It is well-structured and easy to parse, conveying maximum information in minimal space.
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 is simple (one parameter, no output schema), and the description explicitly lists the returned fields, which helps an agent construct a request. However, it omits failure behavior, prerequisites (e.g., using check_book_exists first), and any output structure details, leaving notable gaps for an agent to handle correctly.
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%; the slug parameter is already documented with a description and example. The tool description adds no additional parameter details beyond referencing 'a book', and the schema already provides sufficient semantics.
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 the tool's purpose with a specific verb ('Get') and resource ('a book's summary'), and enumerates the exact fields returned (title, word/page counts, sales, download URLs). This distinguishes it from sibling getters like get_royalties or get_coupon without needing to inspect schemas.
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 guidance is provided on when to use this tool versus alternatives such as preview_book, check_book_exists, or get_royalties. The description only states what it does, leaving the agent to infer selection criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.