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

No annotations are provided, so the description carries the full burden. It implies a read-only lookup via Open Library and signals that multiple books with rich metadata come back, but it never states auth requirements, rate limits, whether matching is fuzzy or exact, or how results are ordered.

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 tight sentences with the core action and scope front-loaded, followed by a payload summary. The long enumeration of returned fields is somewhat list-heavy but reads efficiently.

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?

An output schema already exists, so the extended field list ('authors, first publication year, editions, pages, ISBNs...') is largely redundant. Meanwhile the query syntax and limit behavior, which the schema does not document, are left unexplained, so the effort is misallocated for a two-parameter tool.

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 0%, so the description must explain both parameters. 'By title, author or ISBN' partially documents q's semantics, but there is nothing on whether q may combine fields, on quoting/syntax, or on what 'limit' (default 10) controls or caps.

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?

States a specific verb and resource ('Find books') plus the accepted lookup keys (title, author, ISBN) and the backing source (Open Library). No sibling tool covers books, so it is trivially distinguishable from the rest of the catalogue.

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?

'Use for book lookups, reading lists or metadata' gives clear positive usage context. It stops short of exclusions or alternatives (e.g. when to prefer research_papers or wikipedia_summary), so it does not reach a 5.

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