Add To Collection

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

Annotations already declare readOnlyHint=false and destructiveHint=false. The description adds the constraint that the item must already exist and that the key comes from search results, which are useful preconditions. However, it does not disclose edge-case behaviors like duplicate handling or idempotency, so it only modestly exceeds the annotation baseline.

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 sentence with a clear verb and object, followed by a terse parameter list. Every element earns its place, and it is front-loaded with the main purpose.

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 2-parameter tool with annotations and an output schema, the description covers purpose and parameter meaning. It lacks explicit guidance on duplicate handling or when-then workflows, but these are minor given the tool's simplicity.

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 coverage is 0%, so the description fully carries the burden. It explains item_key as 'The Zotero item key (from search results)' and collection_id as 'The collection key to add it to', adding meaning beyond the bare schema titles.

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 'Add' and clearly names the resource 'an existing Zotero item to a collection'. This distinguishes it from sibling tools like remove_from_collection or create_collection.

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 (adding an existing item to a collection) but provides no explicit guidance about when to use this tool versus alternatives, nor does it mention prerequisites like needing to search for the item first. The parameter note 'from search results' hints at a workflow but is not a full usage guideline.

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