Add Book By Isbn

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the write and external-network nature is known without the description. The description adds the specific source (Open Library metadata resolution) and that a new item is created, which is useful context. It says nothing about duplicate-ISBN handling, permissions, or failure behavior, so with annotations carrying the safety burden a 3 is appropriate.

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?

Purpose is front-loaded in the first sentence, followed by mechanism and optional behavior, then a compact Args block. No wasted sentences. The Args section only covers 2 of 4 parameters, which is a completeness issue rather than a verbosity one.

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?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. But with 4 parameters at 0% schema coverage, the omission of library_id and library_type leaves an agent unable to tell how to target a group library vs a user library. Minimum viable but noticeably incomplete.

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 0%, so the description carries the full burden, yet it documents only isbn (with a format example) and collection_id. The library_id and library_type parameters appear nowhere, leaving half the parameters with no semantics at all. It partially compensates but falls well short of what 0% coverage requires.

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+resource+identifier scheme (add a book by ISBN to Zotero), which naturally distinguishes it from the sibling family (add_paper_by_doi, add_paper_by_arxiv_id, add_item_from_metadata). It also specifies metadata resolution via Open Library and optional collection placement. However, it never explicitly contrasts itself with those siblings, so it stops short of a 5.

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?

Usage is implied by the ISBN-based identifier and the 'optionally add it to a specific collection' clause, but there is no explicit when-to-use guidance, no statement of when to prefer add_item_from_metadata or add_paper_by_doi instead, and no prerequisites declared. Adequate but with clear gaps.

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