zotero_bulk_update_fields

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

With no annotations provided, the description carries the burden of disclosing behavior. It does so by stating this is a field-patch write operation, noting each entry carries its own Zotero-Write-Token for idempotency, and clarifying that per-item semantics match zotero_update_item_fields. It does not address partial-failure behavior or batch limits, but the core mutation and idempotency traits are made visible.

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 compact and front-loaded: it states the bulk purpose, gives a realistic example, connects to the single-item sibling, and mentions idempotency. Every sentence contributes useful information with no filler.

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?

For a bulk mutation tool with one parameter, the description covers purpose, item format, per-item semantics, and idempotency. An output schema exists, so return-value details need not be in the description. The main missing piece is behavior on partial failures, but the per-item token wording partially mitigates that ambiguity.

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 100%: the schema already documents updates as 'Entries of {key: item key, fields: fields to change}.' The description adds a concrete key example and the phrase 'fields: {...}' but does not meaningfully go beyond the schema, so the baseline of 3 is appropriate.

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 uses a specific verb plus resource: 'Apply a field patch to MANY items in one call,' with a concrete example. It also directly distinguishes itself from the single-item sibling zotero_update_item_fields by emphasizing bulk behavior, so an agent can tell them apart without opening schemas.

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 clearly signals when to use this tool: when updating many items at once, such as 'fixing a hundred titles.' It references zotero_update_item_fields for per-item semantics, which implies the alternative for single-item updates, though it does not explicitly say 'do not use this for one item.'

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