zotero_create_collection

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

With no annotations provided, the description carries the full burden and does a solid job: it discloses the creation behavior, the optional parent nesting, the idempotent duplicate handling (returns existing key), and the return value (collection key). It omits topics like authentication requirements or error behavior, but for a create tool the disclosed traits are relevant and concrete.

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 three tight sentences: purpose, duplicate behavior, return value. There is zero filler, and the core action is front-loaded. Every sentence earns its place and adds distinct information.

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 simple parameter set (3 params, 100% schema coverage, no nested objects) and no output schema, the description covers the critical return value and the non-obvious idempotency behavior. It is complete enough for an agent to call correctly; the only minor gap is the lack of explicit error/edge-case handling, which is not essential for this straightforward create operation.

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?

The input schema already covers all three parameters with 100% description coverage, including the special path format for 'parent' and library selection variants. The description adds context about the duplicate check being 'under that parent', but it does not add significant new parameter-level meaning beyond what the schema provides. Baseline 3 is appropriate.

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 opens with a specific verb and resource ('Create a collection (folder)') and immediately adds the key differentiator of optional nesting under a parent. The 'create' action clearly separates it from siblings like zotero_update_collection and zotero_delete_collection, and the duplicate-handling behavior further distinguishes it from a plain create.

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 when to use the tool ('create a collection') and even notes the idempotent duplicate behavior, which suggests it can be used to ensure a collection exists. However, it never explicitly names alternatives or states when not to use it (e.g., 'use zotero_update_collection to modify an existing collection'), so the guidance is implied rather than explicit.

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