zotero_remove_from_collection

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

With no annotations, the description carries the full burden. It discloses that items stay in the library (a key behavioral trait), but omits other important aspects for a mutation tool, such as required permissions, reversibility, or what happens if an item is not in the collection. This is a minimal disclosure beyond the core function.

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 two short sentences with no filler. The primary action is front-loaded, and the clarification about items staying in the library is valuable and placed efficiently. Zero waste.

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 simple removal operation with only 3 parameters and no output schema, the description covers the core purpose but lacks details on edge cases, return values, or prerequisites. However, the schema is comprehensive, so the description is adequate but not thorough.

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%, with each parameter (keys, library, collection) already described. The tool description adds no additional meaning beyond what the schema provides, so the baseline score of 3 applies.

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 uses a specific verb ('take items out') with a clear resource ('a collection') and explicitly states that items remain in the library, distinguishing it from deletion tools like zotero_delete_collection or zotero_trash_items. This makes the 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?

The description implies when to use this tool (removing items without deleting them) but does not explicitly name alternatives or state when not to use it. It clarifies the non-destructive nature, which implicitly differentiates it from deletion tools, but lacks direct exclusions or selection criteria.

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