Add Book By Isbn

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

Annotations already indicate this is a write operation (readOnlyHint=false) with potential side effects (openWorldHint=true). The description adds that it 'Resolves metadata automatically via Open Library', disclosing an external network dependency, and that it creates the item in Zotero. It doesn't describe failure modes or duplicate handling, but with annotation coverage, this is sufficient.

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 compact and front-loaded, with a clear 'Args:' section. Every sentence serves a purpose: what it does, how metadata is resolved, and optional collection. No redundancy.

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?

The tool has an output schema, so return values need not be described. The description covers the main workflow: input ISBN, metadata resolution, item creation, optional collection assignment. It omits edge-case warnings like invalid ISBNs or network failures, but for a tool of this complexity, it's reasonably complete.

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 no descriptions (0% coverage), so the description compensates by explaining isbn as 'The ISBN of the book' with an example and collection_id as 'Optional Zotero collection key'. This adds practical meaning beyond raw schema types, though it could be more specific about ISBN format or collection key length.

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 states the tool adds a book to Zotero by ISBN, with a specific verb ('Add'), resource ('book'), and method ('by its ISBN'). It distinguishes from siblings like add_paper_by_doi by naming the ISBN-based approach.

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 description gives context: use this when you have an ISBN and want automatic metadata resolution via Open Library, and optionally specify a collection. It doesn't explicitly name alternatives or state when not to use, but the ISBN specificity differentiates it from DOI/arXiv siblings. No exclusions.

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