Create or update Zotero items

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

The description adds behavioral details beyond annotations: server auto-chunks into groups of 50, all-or-nothing validation, and requires ZOTERO_API_KEY. Annotations only indicate it's not read-only (readOnlyHint=false) and accepts arbitrary data (openWorldHint=true). No contradictions.

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 a single, well-structured paragraph. It front-loads the main action and then details structure and behavior. Every sentence adds value, though it could be slightly shorter. No waste, but room for minor tightening.

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 has 3 parameters and no output schema, the description covers the essential aspects: batch size, update vs create, validation, and external schema reference. It does not describe return values or error details beyond 'problems are returned', but for a data entry tool this is acceptable.

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 low (33%), so the description must compensate. It explains the structure of the `items` array: itemType, creators, tags, collections, and the distinction between create and update (key+version). It does not describe `library_id` or `library_type`, but these are less critical. Overall, it adds meaningful meaning beyond the sparse schema.

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 tool's purpose: 'Create new items or update existing ones in a single batch'. It specifies the resource (Zotero items) and the action (create/update batch). This distinguishes it from siblings like zotero_update_item (singular update) and zotero_schema (schema discovery).

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 clear context: it's for batch operations, with auto-chunking, and refers to zotero_schema for field discovery. It explains when to use update vs create by including key+version. However, it doesn't explicitly mention alternatives like zotero_update_item for single updates, leaving some ambiguity about when not to use this tool.

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