get_editions_by_isbn

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

With no annotations, the description carries full burden, yet it only says 'look up an edition.' It does not disclose whether authentication is needed, how results are returned, what happens on invalid ISBNs, or which specific matching behavior is used.

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 short sentence contains the core action and input format. No filler or repeated schema content, and the key lookup target is front-loaded.

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 single-parameter lookup, the description is adequate on the surface, but the plural tool name and singular 'an edition' create ambiguity. Without an output schema or additional details on return structure, an agent may not know whether this returns one edition or many matches.

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 description coverage is 100% and the parameter description already specifies format and constraints. The description adds only ISBN-10/13 detail that is mostly redundant, so it stays at the baseline rather than adding new semantics.

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 clearly names the operation ('Look up') and resource ('an edition by ISBN-10 or ISBN-13'), which distinguishes it from sibling lookup tools like get_edition_by_id or get_editions_by_title. It is slightly vague about whether one or many editions are returned, matching the plural function name.

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 'by ISBN-10 or ISBN-13' implies the primary use case: when an agent has an ISBN. However, there is no explicit guidance on when to choose this tool over alternatives, and no exclusions or fallback recommendations.

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