find_books_for_topicMatch a topic or question area (for example: agent reliability, prompt injection, human in the loop, durable execution, when to trust AI) against the catalog's curated topic map. Returns the matching topics with their books, guide, and series. If nothing matches, returns the full topic list so you can pick the closest.
| Name | Required | Description | Default |
|---|---|---|---|
| topic | Yes | The topic phrase to match. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden and discloses two important behaviors: it maps to a curated topic map, and if nothing matches, it returns the full topic list so the agent can pick the closest. It does not cover all edge cases (e.g., exact output shape), but the core edge-case behavior is transparent.
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?
Three sentences, each carrying distinct information: input examples, return content, and fallback behavior. No filler, and the most important action is front-loaded.
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 one-parameter lookup with no output schema, the description covers the input semantics, what the result contains (books, guide, series), and the no-match behavior. Nothing an agent needs to invoke it correctly or interpret the result 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?
The schema covers the single parameter with a minimal description, providing a baseline of 3. The tool description adds value by giving concrete example topic phrases ('agent reliability, prompt injection, human in the loop') and clarifying that the parameter accepts a topic or question area, not just an exact title.
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 uses a specific verb ('match') against a defined resource ('the catalog's curated topic map') and states the output (matching topics with books, guide, series). It clearly describes the tool's function, though it does not explicitly differentiate it from the sibling search_greenlit_books, so it stops short of a 5.
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 implies when to use the tool: when you have a topic or question area to match against the catalog. It provides no explicit guidance on when not to use it or which sibling tool to prefer, such as search_greenlit_books for keyword-based book 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.
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.