add_to_collection

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

Annotations already signal a non-destructive, idempotent write (readOnly=false, destructiveHint=false, idempotentHint=true), so the bar is lower. The description adds concrete behavioral detail: adding to a collection does not remove the item from other collections. It does not mention error cases or duplicate handling, but that is minor given the annotation coverage. No contradiction.

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 short, purposeful sentences. The action is front-loaded in the first sentence, and the second adds a meaningful use case without redundancy. Every word earns its place.

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 two-key operation with an output schema present and annotations covering safety and idempotency, the description provides the essential semantic and scenario details. It lacks explicit guidance on key sources or edge cases, but the simplicity of the tool and the annotation coverage make this a minor gap rather than a blocking one.

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. It does identify item_key as referring to an existing Zotero item and collection_key as referring to a collection, but it does not explain key format, provenance, or any constraints. This is partial compensation only; the agent still has to infer key details from naming and domain knowledge.

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 opens with a specific verb 'Add' and identifies both operands: an existing Zotero item and a collection. It explicitly contrasts with moving by stating 'without moving it from other collections', which distinguishes it from sibling tools like create_item or batch_organize. An agent can immediately understand what this tool does.

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?

'Use this to organize a paper into a folder' provides a clear, explicit use case, and 'without moving it from other collections' clarifies the boundary of the operation. It does not explicitly name alternative tools or state hard when-not-to-use conditions, but the context is strong enough for an agent to decide when to invoke it.

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