remove_from_collection

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

With no annotations provided, the description carries full burden. It discloses a key behavioral trait: the operation removes from collections but doesn't delete items, which is valuable context. However, it lacks details on permissions needed, error conditions, or what happens if the item isn't in the collection, leaving gaps in behavioral understanding.

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 single, efficient sentence with zero waste. It front-loads the core action and clarifies a critical distinction, making it highly concise and well-structured for quick comprehension.

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?

Given the tool has an output schema (which handles return values) and no annotations, the description is moderately complete. It covers the primary purpose and a key behavioral nuance, but for a mutation tool with 0% schema coverage, it should ideally include more about parameter semantics or error handling to be fully adequate.

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 0%, so the description must compensate for undocumented parameters. It mentions 'item_key' and 'collection_key' implicitly but provides no semantic details (e.g., format, source, or examples). This adds minimal value beyond the schema's structural definition.

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 specific action ('Remove') and target ('a Zotero item from a collection'), while explicitly distinguishing it from sibling tools by noting it 'does not delete the item' (unlike delete_item). This provides precise verb+resource differentiation.

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 usage context by specifying it removes from collections without deleting items, which helps differentiate from delete_item. However, it doesn't explicitly state when to use this versus alternatives like update_item for other modifications or provide prerequisites for the item/collection keys.

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