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

With no annotations and no output schema, the description carries the full burden of explaining behavior, but it discloses nothing: no side effects, no input expectation, no return type, no edge cases. There is no contradiction with annotations because there are no 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?

The description is extremely short, but this is under-specification rather than conciseness; 'Is Isbn13:' adds nothing and the repeated phrase wastes the only available explanatory space.

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 tool with no annotations, no output schema, and a hidden/implied input, the description must explain what 'Is Isbn13' does, what it accepts, and what it returns. It provides none of this, so an agent cannot correctly select or invoke it.

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?

The input schema has zero properties, so there are no parameter semantics for the description to clarify. Per the baseline for 0-parameter tools, this dimension is not penalized despite the otherwise useless description.

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 is a pure tautology: 'Is Isbn13: Is Isbn13' restates the tool name without a verb, subject, or resource. It also fails to distinguish this from numerous similar siblings such as x402-isbn, x402-isbn-validate, and x402-isbn10.

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 guidance about when to call this tool instead of its many ISBN/EAN sibling tools, and no conditions or alternatives are mentioned. An agent gets zero decision support.

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