Rename or move a collection

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

Discloses important runtime behavior not present in annotations: automatic fetching of the current version, optional expectedVersion for conflict detection, and that the write fails with a conflict if the collection changed in the meantime. This adds concurrency semantics beyond the idempotentHint and destructiveHint flags. No contradiction.

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 focused sentences: main operation, null-parent special case, and version conflict behavior. No filler, and key information is front-loaded.

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?

With five parameters, a full input schema, and an output schema present, the description covers the non-obvious semantics (root move, conflict failure) while leaving field-level details to the schema. An agent has everything needed to invoke it 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?

Schema description coverage is 100%, so the description doesn't need to repeat parameter docs. It still adds value by explaining the parentCollectionKey=null root-moving mechanic and the behavioral effect of expectedVersion (failure on concurrent modification), elevating it above the baseline.

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 names the exact verbs ('Rename', 'move') and the resource ('a collection'), and makes clear both actions can be combined. This clearly separates it from sibling tools like zotero_create_collection or zotero_delete_collection without requiring schema inspection.

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 defines the situations for this tool: rename and/or reparent a collection, with explicit instructions for moving to root via parentCollectionKey=null. It does not explicitly name excluded alternatives, but the action domain is clear enough to route an agent correctly.

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