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

With no annotations, the description must disclose behavior fully, but it only says 'value discarded' and 'digit shape'. It does not explain what the tool returns (e.g., a boolean), how it processes the various inputs, or which parameter is actually checked. The lack of detail about the relationship between the parameters and the ISBN-13 check is a significant transparency gap.

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 ('ISBN-13 digit shape, value discarded'), which is concise but under-specified. It lacks any structural elements like context, usage, or return behavior. While brevity is a virtue, here it sacrifices necessary information for a tool with 9 parameters.

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?

Given the tool's complexity (9 parameters, no output schema, no annotations), the description is grossly incomplete. It does not identify the expected input type, the return value, error behavior, or how the ISBN-13 check applies to the listed parameters. An agent cannot reliably select or invoke this tool based on this minimal information.

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% with detailed per-parameter descriptions, so the baseline is 3. However, the tool description does not clarify how these parameters relate to ISBN-13 checking, and the schema descriptions themselves ('Git ref name; discarded after the shape check', 'City name for a public weather hint', etc.) are mismatched with the stated purpose. The description adds no semantic value to the schema and actively confuses the mapping.

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 states 'ISBN-13 digit shape, value discarded' which implies a check on whether an input matches the ISBN-13 format, but it does not specify which of the 9 parameters is the target. The parameter names (ref, url, city, feed, host, json, path, zone, query) are unrelated to an ISBN, making the purpose confusing and ambiguous. It is not a tautology but fails to clearly identify the resource being checked.

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?

No guidance is provided on when to use this tool or when not to. It does not mention alternatives or conditions for selection. The description gives no context for when an agent should invoke this tool among its many siblings, leaving the usage entirely unclear.

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