Zotero Update Collection

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

No annotations are provided, so the description carries the full behavioral burden, and it delivers: it states that identity and nested contents survive the operation, defines the no-op semantics of omitting a field, and gives the cycle-prevention rule for moves. It does not mention write authorization or whether the tool is local-only, which the sibling zotero_authorize_local_writes implies matters.

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?

Front-loads the operation before the parameter glossary, and every clause is information-bearing (constraints, defaults, example). It is dense and the parenthetical issue reference (#517) adds little for an agent, but nothing is wasted at length.

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?

Covers the mutation's semantics, parameter contract and constraints, and an output schema exists so return values need no explanation. The only omission is authorization expectations for a write tool in a server that exposes zotero_authorize_local_writes.

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 0%, so the description is the only documentation, and it documents all four parameters: collection_key is an 8-character key, name is the replacement name or omit-to-keep, parent_collection accepts key/name/'Parent/Child' path, and to_top_level detaches from any parent. The mutual-exclusion/at-least-one-change rule is also spelled out.

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?

Opens with a precise verb+resource+scope: rename or re-parent a collection, and it explicitly notes what is preserved (key, subcollections, item membership). An agent can distinguish this from zotero_create_collection, zotero_delete_collection and zotero_batch_update without opening any schema.

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?

Gives a concrete prerequisite ('Use zotero_search_collections to find keys'), an operating constraint ('a collection cannot be moved under itself or one of its own subcollections'), and a required condition ('Pass at least one change'). It does not explicitly route away from adjacent tools like zotero_batch_update, so it stops just short of fully explicit alternative selection.

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