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

With no annotations, the description carries the full burden, and it does disclose the checksum algorithm (mod-10 alternating weights) and input precondition, plus the commercial model ('5 free trial calls per signed wallet'). What it omits is the return shape (presumably a boolean) and error behavior for values that are not 13 digits, so the disclosure is partial.

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?

A single front-loaded sentence followed by a short pricing note; nothing is buried or padded. The emoji/badge is informational rather than wasteful, though it slightly dilutes an otherwise tight definition.

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 simple boolean check with one parameter and no output schema, the definition covers purpose, input format, and algorithm, which is most of what an agent needs. The main remaining gap is an explicit statement of the returned value and behavior on invalid input.

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?

There is a single unnamed-in-schema parameter ('value') with 0% description coverage, so the description must compensate. It does constrain the format ('hyphen-stripped 13-digit ISBN'), which is real added meaning, but it never ties this to the parameter itself or explains accepted variants.

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 gives a specific verb ('checks whether') and a precisely scoped resource ('hyphen-stripped 13-digit ISBN'), which cleanly separates it from the ISBN-10 and generic ISBN validator siblings. It even names the check algorithm, so an agent can tell it apart from x402-isbn-validate without opening a schema. It stops short of naming a sibling explicitly, so it lands at 4 rather than 5.

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 phrase 'hyphen-stripped' is an implicit precondition that tells the caller to strip hyphens before invoking, which is genuinely useful. However, there is no guidance on when to prefer this over x402-is-isbn10, x402-isbn-validate, or x402-validate-isbn, and no statement of what happens on malformed input. Usage is implied rather than spelled out.

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