zotero_tag_items

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the operation but does not mention whether existing tags are preserved, whether add and remove are mutually exclusive, what happens on partial failure, authentication requirements, rate limits, or any side effects beyond the stated action.

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, efficient sentence that front-loads the core action and scope. Every word earns its place, with no fluff or repetition of schema details.

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 mutation tool with no annotations and no output schema, the description is minimally viable: it conveys the purpose and the schema covers parameters. However, it lacks any mention of return behavior, error cases, or side effects, so it is not fully self-sufficient contextually.

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%, with each parameter already documented ('Tags to add', 'Item keys', 'Tags to remove', 'Library to use'). The description reinforces the batch nature of the call but does not add material meaning beyond the schema, such as behavior when both add and remove are supplied.

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/or remove') with a clear resource ('tags on many items') and context ('via the web API'). This directly conveys the tool's batch behavior and distinguishes it from sibling tag operations like zotero_rename_tag or zotero_delete_tags.

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 phrase 'on many items at once' implies a batch use case, but the description does not explicitly state when to prefer this over alternatives such as zotero_update_item or zotero_delete_tags. There is no exclusion or conditional guidance, so usage context is only implicit.

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