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 two genuinely useful behaviors: hyphens are stripped before validation and the checksum algorithm used (mod-11 for ISBN-10, mod-10 for ISBN-13). It also surfaces a cost/access constraint ('5 free trial calls per signed wallet'). It stops short of saying what the response looks like (valid/invalid flag, extracted digits, error on malformed input), so it is useful but incomplete.

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?

One compact sentence front-loads the verb, resource, accepted lengths, and normalization rule. The trailing promotional emoji/offer is slightly off-topic but short and does convey an access limit.

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, annotation-free validator with no output schema, the description covers input format, normalization, algorithm, and pricing, which is reasonable. It still leaves the return value and failure behavior undocumented, which an agent needs in order to interpret a result.

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 compensate. It does clarify the single input's semantics somewhat: the value is an ISBN string that may contain hyphens, of length 10 or 13. That is meaningful beyond the bare `{value: string}` schema, but it omits whether the ISBN-10 X check digit is accepted and whether prefixes like 'ISBN:' are tolerated.

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 ('Validates a 10- or 13-digit ISBN') and even the method (mod-11/mod-10 checksums), which is more than most validation siblings get. However, the crowded sibling set contains x402-isbn, x402-validate-isbn, x402-is-isbn10 and x402-is-isbn13, and the description makes no attempt to say how this differs from those, so the agent cannot disambiguate on the description alone.

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?

There is no when-to-use or when-not-to-use guidance, and no mention of the closely overlapping siblings (x402-isbn, x402-validate-isbn, x402-is-isbn10/13). Nothing tells the agent which of these ISBN tools to pick for a given need.

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