zotero_manage_collections

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

No annotations provided, so description carries burden. Discloses that invalid specs cause failure before changes, but no information about authorization, rate limits, or other behavioral traits. Adequate but not thorough.

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?

Three sentences, front-loaded with purpose, no unnecessary words. Each sentence adds value: purpose, parameter format hints, and cross-reference to sibling tools.

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 existence of output schema, description need not cover return values. Covers purpose, parameter details, and constraints. Missing behavioral aspects like mutation safety or concurrency, but context signal complexity is moderate.

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%, requiring description to compensate. Description explains formats for add_to and remove_from (keys, names, paths), but contradicts schema by stating item_keys must be an array while schema also allows a string. This confusion reduces clarity.

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?

Description clearly states the tool adds or removes items from collections, using specific verbs and resources. It distinguishes from sibling tools like zotero_search_items and zotero_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?

Provides guidance to use zotero_search_items and zotero_search_collections to find keys. Explains that unknown or ambiguous specs fail before changes. Lacks explicit when-not-to-use, but sufficient for selection.

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