zotero_update_item

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

With no annotations, the description carries the disclosure burden, and it does disclose the key behavioral trait: partial-update semantics ('Only the fields you pass are changed') plus the destructive actions of clearing fields and replacing creators. It does not cover permissions or errors, but the mutation scope is clearly stated.

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?

A single, well-structured sentence states the action first, then the scope of changes, then the critical partial-update caveat. There is no filler or redundant material.

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?

The description covers the invokeable operation well, but with no annotations and no output schema it omits the return value/confirmation behavior, possible error conditions, and prerequisites such as authentication or item ownership. For a 6-parameter mutation tool, some of this context is still missing.

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 67%, so the description adds value by listing representative fields, stating that creators are replaced, and explaining add/remove tag behavior. It complements the schema's fields example and creator format rather than repeating them exactly.

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?

Description begins with a specific action and resource ('Edit an existing item's metadata via the web API') and enumerates exactly what can change: fields, creators, and tags. This clearly differentiates it from create, tag-only, and collection update siblings.

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?

There is no explicit when-to-use or when-not-to-use guidance and no mention of alternatives such as zotero_create_item or zotero_tag_items. The word 'existing' implies it is not for creating items, but the agent must infer that rather than being told.

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