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

Beyond readOnlyHint/openWorldHint, it discloses the commercial model ($0.002 USDC via x402 on Base/Solana/Arc), that failed calls are not charged, that a missing title is a 404 rather than a billable miss, the 20-result cap, and the CC0 Open Library provenance. These are concrete operational traits an agent cannot get from annotations.

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?

Purpose and lookup modes are front-loaded, and the closing sentences carry pricing and error semantics efficiently. The long enumeration of returned fields is somewhat redundant given an output schema exists, which costs a little economy.

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 annotations covering safety, an output schema covering return shape, and a fully described schema, the description still supplies the missing pieces: payment mechanism, billing on failure, 404 semantics, and result caps. Nothing an agent needs before calling is absent.

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%, so the schema already documents isbn, limit, title and author. The description adds only that ISBN is validated before the call and that results cap at 20, which maps to the limit parameter but adds no new format or interaction rules.

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 ('Book lookup by ISBN ... or by title and/or author') and names the exact retrieval modes. It is clearly distinguishable from sibling bibliographic tools such as doi, arxiv, wiki, and wikidata.

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?

Gives clear selection context: use ISBN when already known, otherwise title and/or author, and warns that a non-matching title returns 404. It does not name an alternative sibling for cases where a different lookup source is better, so it stops short of full when/when-not routing.

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