search_books

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It does not mention read vs. write behavior, potential performance impacts, or what happens with invalid queries. The description focuses on syntax examples but lacks transparency on side effects or limitations.

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 front-loaded with the tool's purpose, then provides structured examples and parameter explanations. It is concise but each section adds value. Minor improvement: the 'Args' section repeats parameter info partially redundant with schema.

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?

Given the complexity (search syntax) and that an output schema exists (reducing need to describe return values), the description covers query usage well. However, it lacks information about error handling or behavior when no results match.

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 description explains the query parameter with syntax examples, adds meaning for fields, limit, and sort_by beyond the schema (which has no descriptions). With 0% schema coverage, the description compensates well for most parameters, though it could clarify acceptable values for fields and sort_by.

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 that the tool searches books using Calibre's search syntax. It specifies the resource (books) and the action (search), and distinguishes from siblings like get_book_info which retrieves info for a specific book.

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 provides examples of search syntax and parameters, implicitly guiding usage. However, it does not explicitly state when to use this tool versus alternatives (e.g., get_book_info for specific books), nor does it mention any prerequisites or caveats.

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