Edit fields on a Zotero item

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

Beyond the destructiveHint annotation, the description reveals a meaningful concurrency safeguard: it reads the current version and sends If-Unmodified-Since-Version so a concurrent edit fails rather than overwriting. It also exposes dry_run as a no-write preview, giving an agent the full behavioral picture.

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 well structured: a one-line purpose, a short concurrency note, then Args and Returns. Every sentence serves a distinct purpose and there is no redundant 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 three-parameter mutation tool, the description provides all the necessary invocation details, including the return summary and the concurrency behavior. It could additionally list which metadata fields are valid or how conflicts are surfaced, but that is not strictly required to call the tool correctly.

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 schema description coverage at 0%, the Args block compensates fully: item_key is defined as the key of the item to edit, fields_json gets a concrete JSON example ('{"volume": "12", "pages": "45-58"}'), and dry_run is explained as showing the change without writing. Every parameter receives meaning beyond its title.

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 starts with 'Change one or more metadata fields on an existing item,' which is a clear verb+resource statement that distinguishes editing from adding or searching. It does not explicitly name a sibling alternative, so it falls just short of the strongest differentiation.

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 makes clear this tool is for modifying existing item metadata via fields_json, and the 'existing item' wording implies not for creation. However, it offers no explicit when-to-use guidance, exclusions, or pointers to sibling tools like zotero_add_item or zotero_manage_tags.

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