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 burden of behavioral disclosure. It clearly states the mutation (rename/move) and the 'root' special value for top-level placement. However, it does not disclose whether the operation is destructive, whether the old parent is removed, whether the collection key remains stable, or whether permissions are required. For a mutation tool with zero annotations, this is a moderate gap.

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 sentence that front-loads the primary action ('Rename a collection') and then adds the secondary action ('and/or move it under another parent'). Zero waste, and the 'via the web API' context is useful for distinguishing from local operations.

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 4-parameter mutation tool with no output schema and no annotations, the description is adequate but not complete. It explains the two operations and the 'root' special value, but it does not mention return values, error conditions, or the effect on child collections when reparenting. An agent could call it correctly for a simple rename, but might be uncertain about edge cases.

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 schema already documents all four parameters. The description adds the 'root' special value for top-level placement, which is useful, but it does not add meaning beyond the schema for the other parameters. Baseline 3 is appropriate when the schema does the heavy lifting.

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 states a specific verb ('Rename') and resource ('a collection'), and explicitly covers the second operation ('move it under another parent or to the top level'). It clearly distinguishes this from sibling tools like zotero_create_collection, zotero_delete_collection, and zotero_add_to_collection by naming the exact mutations performed.

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 implies when to use this tool: when renaming or reparenting a collection. It does not explicitly state when not to use it or name alternatives, but the sibling list makes the distinction fairly clear. A brief exclusion note (e.g., 'to add items to a collection, use zotero_add_to_collection') would make this a 5.

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