zotero_update_item_fields

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

With no annotations provided, the description carries the full burden. It discloses the partial-update behavior ('Pass only the fields to change; everything else is untouched') and the tag format. It does not state reversibility, error handling, or any permission requirements, but the key mutation semantics are covered.

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?

Three concise sentences, each earning its place: purpose with examples, the partial-update behavior, and the prerequisite plus exclusion. No filler or redundancy.

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 simple two-parameter update tool with a detailed schema, the description covers purpose, partial-update semantics, tag format, a prerequisite, and an explicit exclusion of collections. It misses a note about changing item type being handled by a separate tool (zotero_change_item_type), and the tag replacement behavior is not specified, but overall it is adequate.

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?

The schema already documents both parameters reasonably well (fields with a JSON example, item_key as a string). The description adds value beyond the schema by explaining the partial-update rule and providing the exact tag format (tags: [{'tag': 'x'}]).

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 states a specific verb ('Update fields') and resource ('of an item'), with concrete examples (title, date, publication, abstract, tags). It clearly implies a single-item operation, distinguishing it from the bulk-update sibling by name and scope, and explicitly excludes collections.

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?

Provides explicit guidance to first use zotero_item_metadata to see current values, and clearly states collections are NOT edited here, directing to dedicated collection tools. However, it does not explicitly mention when to use this vs. zotero_bulk_update_fields for multiple items.

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