zotero_set_item_collections

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it delivers thoroughly. It states that this is an incremental operation ('Existing memberships not named in remove_from are left alone'), discloses validation behavior ('resolved and validated automatically; unknown, trashed, or ambiguous specs fail before anything is changed'), and clarifies atomicity (no partial changes). This is rich, high-value behavioral context.

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 dense single paragraph that front-loads the core purpose and alternates. Every sentence adds value, but it's longer than strictly necessary and could benefit from being broken into shorter sentences for scanability. Still, there is zero fluff or repeated structured data.

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?

This is a mutation tool with no annotations but rich documentation. It covers the operation's nature (incremental), edge-case behavior (validation failures), what it does NOT do (create/delete collections, replace wholesale), data types, and companion tools. The output schema exists, so return-value explanation is not needed. This is unusually complete for the complexity of this tool.

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 coverage is 0%, so the description must compensate, and it does substantially. It clarifies that item_keys must be an ARRAY ('not a single string'), explains that add_to/remove_from accept arrays of collection keys, names, or '/'-separated paths, and explains the semantic difference between the two parameters. It doesn't fully enumerate every edge case of the array/string anyOf types but covers the critical usage semantics.

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 precisely what the tool does: 'Change which collections existing items belong to — an incremental add/remove of item membership.' It uses a specific verb (change/add/remove) with a clear resource (collection membership of existing items), and explicitly distinguishes itself from collection creation, which differentiates it from sibling tools like zotero_create_collection and zotero_delete_collection.

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 gives explicit when/when-not guidance: 'NOT collection creation (use zotero_create_collection / zotero_delete_collection for that)' names the alternatives directly. It also tells the user when to use a different tool for wholesale replacement ('to replace an item's memberships wholesale use zotero_update_item'). It even suggests complementary search tools (zotero_search_items, zotero_search_collections) for finding required keys.

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