search_books

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

No annotations exist, so the description fully bears the burden. It discloses case-insensitive partial search, exact genre filtering, and the behavior of available_only (returns only books with copies). This is adequate for a read-only search tool, though it does not mention return limits or ordering.

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 well-structured docstring with Args and Returns sections, using only two lines of prose plus parameter descriptions. Every sentence adds value, no redundancy.

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 search tool with 3 parameters (none required) and an output schema, the description covers the core behavior, return format (list of books with author), and edge case (empty list). It does not mention pagination or sorting, but the tool's simplicity makes this acceptable.

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 input schema has no description for any parameter (0% coverage). The description compensates fully by explaining each parameter: query for partial case-insensitive title search, genre for exact match (with example values), and available_only as a boolean filter. This adds critical meaning beyond the 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?

The description explicitly states it searches books by title and/or genre, specifying the two search dimensions. Sibling tools like books_by_author and get_book indicate that this tool is distinct in filtering by title/genre rather than author or single book retrieval.

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 clearly outlines the three parameters and their effects (partial case-insensitive search, exact genre filter, availability filter). It does not explicitly state when not to use this tool or compare to alternatives, but the context of siblings combined with the parameter explanations provides sufficient usage guidance.

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