Zotero Set Item Collections

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

With no annotations, the description carries the full burden. It discloses the incremental, non-destructive nature, explains that unknown/trashed/ambiguous specs fail before any changes, and states that unspecified existing memberships are preserved. This gives the agent a clear mental model of side effects and error handling.

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 yet information-dense, front-loading the primary action and differentiation before parameter details. Every sentence contributes value—no fluff or redundancy.

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 tool with 3 parameters, no annotations, and 0% schema coverage, the description covers the operation, alternatives, parameter formats, failure behavior, and key discovery. 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 coverage is 0%, so the description compensates fully. It specifies that item_keys must be an array (not a string), explains that add_to and remove_from accept arrays of keys, names, or paths, and clarifies their role in membership changes. This adds essential meaning beyond the raw schema.

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 clearly states the tool's action: 'Change which collections existing items belong to — an incremental add/remove of item membership.' It explicitly distinguishes from sibling tools like zotero_create_collection, zotero_delete_collection, and zotero_update_item, making its purpose unambiguous.

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?

Provides explicit when-to-use guidance: 'NOT collection creation' and 'to replace an item's memberships wholesale use zotero_update_item.' Also instructs how to find necessary keys via zotero_search_items and zotero_search_collections, leaving no ambiguity about when to invoke this tool versus alternatives.

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