search_books

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses automatic mirror switching, pagination behavior (5 results/page), and returned fields (title, author, etc.). With no annotations, this adequately informs agents of key behaviors, though rate limits or error handling are omitted.

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 succinct sentences, each delivering key information: purpose/behavior in first, result format/pagination in second. No filler or repetition.

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?

Covers core functionality, mirror handling, pagination, and result fields. Lacks details on error states or empty results, but sufficient for typical search tasks given the parameter count and absence of output schema.

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%, so baseline is 3. Description adds no new semantics for parameters beyond what schema provides; 'query' and 'page' are restated, 'extensions' is not mentioned. No value added over schema.

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?

Description clearly states the tool searches for books on Library Genesis, with specific verb 'search' and resource 'books'. It mentions automatic mirror retries, which adds clarity. Sibling tools (download_book, get_formats) indicate distinct purposes, so no confusion.

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 explicit guidance on when to use this tool versus alternatives (download_book, get_formats). While the name implies search, the description does not contrast with siblings or state prerequisites, leaving the agent without context for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.