zotero_add_by_isbn

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

With no annotations provided, the description carries full behavioral burden. It discloses the metadata resolution process (Open Library primary, Google Books fallback) and the response includes the resolver source for auditability. It does not cover error handling or duplicate creation, but the disclosed behaviors are sufficient for a read-only-like creation tool.

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 two sentences, front-loaded with the core action, and contains no redundant words. Every sentence adds value, making it highly concise and easy to parse.

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 are covered elsewhere. The description explains input format and resolution method but does not address potential issues like invalid ISBN errors or duplicate handling. For a creation tool, this leaves some gaps in completeness, though core functionality is clear.

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 must compensate for all parameters. It only explains the 'isbn' parameter's acceptable formats, completely ignoring 'tags' and 'collections'. This omission means the description adds insufficient meaning beyond the schema for two out of three parameters.

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 verb 'Add' and the resource 'a book to your Zotero library by ISBN', which is specific and distinct from sibling tools that use different identifiers. It also details acceptable ISBN formats, further clarifying the tool's purpose.

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 explains when to use this tool (when you have an ISBN) and provides input format guidance. However, it does not explicitly exclude other scenarios or mention alternatives like zotero_add_by_doi for DOIs, leaving usage context implied rather than explicit.

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