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

Beyond the annotations it discloses the upstream source and license (Open Library, CC0), that the check digit is verified before any lookup, that invalid or unknown ISBNs are refused uncharged, and the exact cost model ($0.01/call, first 25 free, failed calls free, repeats not free). Its 'changes nothing' claim is consistent with readOnlyHint=true and destructiveHint=false, and the repeat-charge note matches idempotentHint=false.

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?

Front-loaded with the lookup action and the field list, and the example is placed usefully. It runs long in a single block and the closing 'Reads or computes only and changes nothing' slightly restates what readOnlyHint already declares, but no sentence is filler.

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 one-parameter, no-output-schema tool, the description covers input format, expected output fields, validation behavior, and cost/failure semantics. An agent has everything needed to decide whether to call it and how to interpret a refusal.

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% and the single parameter already documents 'ISBN-10 or ISBN-13, with or without hyphens', so the baseline is 3. The description adds modest value by noting spaces are tolerated and by giving a worked example (isbn=9780140328721), but no format normalization or edge-case rules beyond that.

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 ('Look up a book by its ISBN-10 or ISBN-13') and enumerates exactly what comes back (title, authors, publishers, date, pages, subjects, language, cover, Open Library link), which cleanly separates it from book_search and validate_isbn. It does not explicitly name a sibling it is not, so it stops short of a top score.

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 to enrich a reading list, a product listing or a citation' gives concrete when-to-use contexts, and the ISBN-only input implicitly scopes it away from title/author searching. There is no explicit when-not clause or named alternative, so it is clear context rather than full routing guidance.

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