Update Zotero item

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

The 'optimistic version checking' phrase adds meaningful behavioral context beyond the annotations, suggesting concurrency-aware updates and possible rejection on stale versions. 'Through the authenticated extension' also signals an auth dependency. However, it does not describe what happens on version conflict, whether partial updates are allowed, or what the response contains, so the added value is moderate.

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 concise sentence with no filler, and it front-loads the core action before the mechanism. It is appropriately brief, though the terseness limits how much semantic value it can deliver.

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 3-parameter mutation tool with no output schema, no parameter descriptions, and a nested arbitrary 'fields' object, this description is too thin. It does not explain how to structure fields, what key/version values are expected, or what a caller should expect back, so an agent would lack enough context to invoke it confidently.

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?

With 0% schema description coverage, the description is the only source of parameter meaning. It clarifies that 'fields' are Zotero fields and links 'version' to optimistic checking, but it leaves 'key' completely unexplained and gives no detail about the shape of the nested 'fields' object, which is a significant gap.

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 identifies the action ('Update'), the target ('Zotero fields'), and a distinguishing mechanism ('optimistic version checking'). This is fairly clear, but it does not explicitly differentiate itself from sibling mutation tools like zotero_add_tags or zotero_create_item beyond the implied item-scope, so it falls just short of a 5.

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?

No guidance is given on when to use this tool versus alternatives such as zotero_create_item, zotero_add_tags, or zotero_attach_link. The phrase 'optimistic version checking' hints at one scenario, but there is no explicit when/when-not or alternative routing, leaving the agent to infer usage.

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