zotero_batch_update

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

No annotations are provided, so the description carries full burden, and it delivers. It discloses that set_keys upserts case-insensitively by key prefix and replaces in place else appends; remove_keys deletes lines while preserving colon-less lines; attachments and unchanged items are skipped and counted; and it requires a writable library. This is rich behavioral context beyond what any schema could convey.

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 dense and packed with meaningful content in a compact form, with the most important action verbs front-loaded. It uses specific technical terms (upsert, ANDed, case-insensitive prefix matching) to communicate efficiently. It's slightly long but every clause earns its place; a minor deduction for a run-on structure that could benefit from splitting.

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 8 parameters at 0% schema coverage, no annotations, and no sibling differentiation needed beyond what's possible, this description is impressively complete. It covers selection logic, action semantics, edge behaviors (attachments, unchanged items), prerequisites (writable library), and provides a full worked example. The output schema exists, so return-value documentation is not needed from the description.

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 for all 8 parameters. It does compensate for most: item_keys, query, tag, add_tags, remove_tags, set_keys, remove_keys, and limit are each described with their semantics. However, the limit default of 50 is noted but not its impact on partial selection beyond 'max items for query/tag selection' — a minor gap since it could note what happens to unprocessed items.

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, high-value statement: 'Edit metadata across many items in one call: add/remove tags and upsert/remove `Key: value` lines in Extra'. It clearly distinguishes this batch mutation tool from siblings like zotero_update_item (single item) and zotero_search_items (read-only search), making it the definitive batch-edit tool.

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 explains the selector logic ('Select items by item_keys, and/or a free-text query, and/or an existing tag; query and tag are ANDed; item_keys wins'), differentiates selectors from actions ('At least one selector AND one action are required'), and clarifies tag behavior ('add_tags/remove_tags keep the item's other tags — not a replace-all'). The inclusion of an example invocation cements when/how to use it.

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