Add items to Zotero collection

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

Annotations already declare this is non-read-only and non-destructive, and the description does not contradict them. It adds useful context that the operation is done through the authenticated extension and only affects existing items, but it does not disclose whether repeated adds are idempotent, what permissions are required, or whether membership is appended or replaced. Given the annotations, this is adequate but not rich.

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?

A single sentence states the action, scope, and authentication context with no filler or repetition. The key qualifier 'existing items' is front-loaded and does meaningful differentiating work.

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-parameter mutation tool with no output schema, the description plus required-field schema gives an agent enough to call it correctly: it names the target resource, the payload role, and the authentication mechanism. It is slightly incomplete in not describing return behavior or edge cases such as duplicate membership, but these are not essential for a basic invocation.

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 explaining collectionKey and itemKeys. It only indirectly clarifies itemKeys by saying 'existing items,' and it never explains that collectionKey identifies the target collection or where these keys come from. The parameter names are suggestive, but the description adds little meaning beyond the raw 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?

The description names a specific verb ('Add') and a precise resource ('existing items to a Zotero collection'), clearly distinguishing it from creation tools like zotero_create_item and zotero_create_collection. It also clarifies that the items already exist, so an agent understands this is an association action, not item creation.

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 intended usage is implied: use this tool to associate already-existing items with a collection, and it mentions the authenticated extension as the access channel. However, it gives no explicit guidance on when not to use it or which sibling tool to prefer for related tasks, such as listing collection contents or creating new items.

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