zotero_add_to_collection

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

With no annotations, the description carries the full burden and covers key behaviors: items can belong to multiple collections, the operation does not remove from other collections, and batching is supported. It does not disclose write-permission requirements or error behavior, but the described traits are the most decision-relevant ones for this additive tool.

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?

Three short sentences, all carrying distinct value: what it does, non-destructive scope, batching, and create behavior. No filler or redundant restatement of the schema.

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 4-parameter tool with 100% schema coverage and no output schema, the description covers the operation's core semantics and key usage tips. It could mention what happens when a key is already in the collection or what the API returns, but these are not essential 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?

Schema description coverage is 100%, so the baseline is 3. The description adds a batching hint for 'keys' and clarifies the effect of 'create=true', but it does not add new meaning for 'library' or 'collection' beyond the 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?

Description opens with a specific verb and resource: 'File existing items into a collection via the web API.' It also clarifies additive semantics ('this does not remove them from others'), which differentiates it from zotero_remove_from_collection and indicates it operates on existing items rather than creating items.

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 concrete usage guidance: 'Works in batches, so pass all the keys in one call' and 'Set create=true to make the collection if it doesn't exist.' It does not explicitly name sibling alternatives or state when not to use it, so it stops short of a 5.

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