zotero_set_item_collections

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states that it can add and remove, but does not clarify whether it fully replaces the collection list, how it handles invalid collection keys, or what effects it has on the item's metadata. This is insufficient for a mutation 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?

The description is a single, front-loaded sentence: 'File a reference into collections, or take it out of them.' It is concise, with no wasted words, and clearly leads with the primary action. The structure is simple and readable, earning every character of its length.

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?

Given the tool has no annotations and a 0% schema description coverage, the description is not complete enough. It does not explain the tool's behavior around add/remove semantics, prerequisites, or side effects. Even though an output schema exists, the lack of behavioral context makes it difficult for an agent to invoke 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 0%, so the description must compensate for the lack of parameter details. However, it makes no mention of the parameters 'item_key', 'add', or 'remove', leaving their roles and formats unclear. The description's generic reference to 'collections' does not map to the specific array parameters or required item_key.

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 'File a reference into collections, or take it out of them' clearly states the tool's action: adding or removing an item from collections. It distinguishes from siblings like create_collection (which creates new collections) and list_collections (which lists collections). However, it uses the informal verb 'file' instead of more explicit terms like 'add' or 'remove', and does not mention the specific parameters.

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 provides no explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or scenarios where another tool (e.g., update_item or create_collection) would be more appropriate. The only implied usage is from the action verb, but no contextual guidance is given.

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