zotero_add_by_isbn

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

No annotations provided, so description carries full burden. Discloses metadata resolution sources, ISBN format acceptance, response includes resolver source, and parameter behaviors. Does not cover error handling or authentication needs, but covers key behavioral aspects.

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?

Single paragraph with efficient sentences; no fluff. Could benefit from bullet points for readability, but remains short and front-loaded with purpose.

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 5 parameters, output schema exists, and sibling tools, the description covers main functionality and parameter details well. Does not discuss error scenarios or metadata quality issues beyond resolver source, but adequate for a tool with output schema.

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 coverage is 0%, but description adds meaning for every parameter: explains isbn formats, collections accepts keys/names/paths, if_exists enum with behaviors, and create_missing_collections as boolean. Particularly detailed on if_exists options.

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?

Clear verb ('Add') and resource ('book to your Zotero library by ISBN'). Distinguishes from siblings like zotero_add_by_doi and zotero_add_by_url by specifying ISBN as the input identifier. Also explains ISBN format flexibility.

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?

Implicitly tells when to use (when you have an ISBN), but does not explicitly mention alternatives like DOI or URL tools. However, provides detailed guidance on if_exists and create_missing_collections parameters, aiding appropriate use.

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