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

No annotations exist, so the description carries the full burden — it does add genuinely useful information in disclosing the cost ('1 credit'), which is not in any structured field. It omits other behavior an agent needs: whether pagination is supported, whether results are capped by default, and how conflicting parameters are resolved.

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 short sentences, front-loaded with the primary capability and no wasted wording; the cost note is a separate parenthetical that earns its place. Slightly under-specified rather than over-long, which is the right failure mode for this style.

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?

With no annotations and no output schema, the description is the only source of behavioral information, and it leaves the key ambiguity of a zero-required-parameter tool unresolved: precedence between isbn and query, and behavior with no arguments. For a simple lookup tool this is a meaningful gap rather than a minor one.

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 description coverage is 100%, so the baseline is 3. The description maps isbn to detail retrieval and query to title/author search, adding a little meaning, but it doesn't clarify whether query matches title and author simultaneously, nor does it explain the limit range (1-25) beyond what the schema already says.

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?

Names a specific verb and resource ('Book details', 'search books') and states the two supported access modes (ISBN lookup vs. title/author search). It does not reference any sibling tool, but none of the listed siblings (wikipedia_summary, arxiv_search, papers_search) overlap directly, so differentiation is less critical here.

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 two modes imply when to use each parameter (ISBN for a known book, query for discovery), but this is inference rather than guidance. It never states what happens if both isbn and query are supplied, or what occurs when neither is, which matters because the schema declares zero required parameters.

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