get_bookThe full record for one Greenlit book by slug: metadata, chapter list, word count, free chapter one, Amazon Kindle and paperback links, prices, Kindle Unlimited status, and related reading.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | The book slug, e.g. claude-code-in-action. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of explaining behavior. It does this well by listing exactly what is returned: metadata, chapter list, word count, free chapter one, links, prices, Kindle Unlimited status, and related reading. It implies a read-only operation, though it does not explicitly mention errors or 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?
The description is a single, well-organized sentence that front-loads the core purpose and then compactly lists the returned contents. There is no redundancy or unnecessary detail.
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 fully covers the return value and invocation context. The schema handles the parameter format, and nothing critical is missing.
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%, so the baseline is 3. The description adds only that the slug identifies a Greenlit book, which the schema already communicates with its example. No deeper parameter meaning is provided.
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 a specific verb and resource: get the full record for one Greenlit book by slug. It enumerates the payload components, clearly distinguishing this from sibling tools like get_free_chapter or search_greenlit_books.
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 makes it clear that this is for fetching a complete book record when you already know the slug. It does not explicitly compare against alternatives or say when not to use it, so it stops short of a 5.
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.
Each tool targets a clearly distinct action: topic discovery, full-text search, book details, concept lookup, free chapter text, and reading paths. The only pair that could overlap—find_books_for_topic and search_greenlit_books—is cleanly separated by curated topic mapping versus ranked full-text search.
Four tools follow the get_* pattern, while the two discovery tools use find_ and search_. This is readable and predictable, with only a minor deviation in verb choice and one name including the server brand.
Six tools is a well-scoped size for a book catalog server. Each tool covers a distinct user need without redundant or bloated surface area.
The surface covers the full reader journey: discover via topic or search, get book details, read the free chapter, understand the concept, and follow a reading path. No obvious dead ends or missing core operations for a catalog-focused server.