add_book

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

No annotations are provided, so the description fully covers behavioral traits: it resolves identifiers into a proper Zotero book item, does not queue/deliver, creates collections on demand, deduplicates by ISBN, and returns closest candidate for loose matches. It warns about corrupting citations.

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 efficient; each sentence adds value. It is front-loaded with the purpose and structured logically: input methods, output type, exclusions, parameter usage, and dedup behavior.

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 (2 params, no annotations, but output schema present), the description covers input, behavior, error handling, dedup, and relationships to other tools. The output schema handles return values, so completeness is high.

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%, but the description adds rich meaning: identifier can be ISBN-10/13, book DOI, or title; collections are for filing topically and created on demand. This fully compensates for the missing schema descriptions.

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 starts with a specific verb-resource pair ('Catalogue a book in Zotero') and lists explicit identifiers (ISBN, book DOI, title), clearly distinguishing the tool from siblings like attach_pdf.

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 provides both when to use (cataloging books) and when not to (never a journalArticle), and gives an alternative (attach_pdf) for putting PDFs on the e-reader. It also explains behavior for loose matches and deduplication.

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