zotero_add_items_to_collection

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

With no annotations provided, the description carries the behavioral disclosure burden. It usefully explains that the operation is non-destructive regarding other collections, which is important behavioral context beyond a simple 'add' statement. It could mention more about error cases or idempotency, but the key behavioral trait is covered.

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?

Two concise sentences with no filler. The core action is front-loaded, the non-destructive caveat is stated clearly, and the practical hint about getting keys is included without bloating the description.

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 straightforward two-parameter tool, the description provides the essential context: what it does, a key behavioral detail, and how to obtain a required parameter value. It does not describe the return value, but that is not critical for invoking the tool 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?

The input schema already documents both parameters well, including an example for item_keys. The description adds value by telling the agent where to get collection keys, but it does not add significant meaning beyond the schema for the parameters themselves.

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 action ('Add one or more items to a collection') and names the exact resource. It also adds a distinguishing semantic detail: an item can be in multiple collections and this operation never removes it from others.

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 concrete usage guidance by pointing the agent to zotero_list_collections for obtaining collection keys. It does not explicitly name alternative tools, but there is no obvious sibling that performs the same operation, so this is sufficient.

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