zotero_add_item

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

With no annotations, the description carries the full burden, and it delivers extensively: it discloses write authorization requirements, file copying into local storage, validation failures for ambiguous collections, idempotency semantics for if_exists='file', and the caveat that URL-derived items may be bare webpages. No contradiction exists.

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 long but every sentence adds functional value. It is front-loaded with the purpose, then systematically covers routing, collections, existence handling, attachment modes, and file specifics. No redundancy or fluff; each clause clarifies a decision the agent must make.

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 (8 parameters, multiple input types, conditional behaviors) and the presence of an output schema, the description covers all necessary operational details: source formats, collection validation, idempotency, attachment modes, and auth requirements. The only omission, tags, is minor and does not hinder correct invocation.

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%, so the description must compensate. It thoroughly explains source, source_type, collections, create_missing_collections, if_exists, attach_mode, and title. The only gap is the 'tags' parameter, which is never mentioned; while its purpose is fairly obvious, the description omits it entirely, a minor but real gap.

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 opens with a specific verb and resource: 'Add item(s) to Zotero from any source' and enumerates supported input types (DOI, URL, ISBN, BibTeX, CSL JSON, local file). It clearly distinguishes this from sibling tools by framing it as the universal add operation and even tells the agent to use it for every 'add this to Zotero' request.

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 explicitly says 'Use for every add this to Zotero request' and provides detailed routing guidance for each source type, including when to prefer a DOI over a URL and when to resolve to a DOI first. It also explains conditional behaviors like if_exists and create_missing_collections, giving the agent clear decision criteria.

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