Create Zotero Collection

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

Annotations already indicate write (readOnlyHint=false), but the description adds context by stating it requires API key write access, mentions error codes (403, 409), and notes the operation is not idempotent. It does not contradict annotations and provides practical behavioral details beyond basic flags.

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 well-structured with sections for args, examples, and error handling. It is informative without being excessively long. Minor redundancy exists with the schema parameter descriptions, but overall every sentence contributes.

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?

The tool is a creation operation with no output schema. The description covers return value, auth prerequisites, duplicate-prevention guidance, and common errors. This is complete enough for an agent to use it effectively, especially given the rich annotations and full schema coverage.

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%, and the description essentially repeats the parameter meanings (name, parent_collection_key). It adds a usage example but no additional semantic depth beyond the schema. Baseline 3 is appropriate given full schema coverage.

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 clearly states this tool creates a new collection (folder) and optionally as a subcollection. It uses a specific verb (create) and resource (collection), and distinguishes itself from siblings like zotero_list_collections and zotero_create_item.

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 explicit usage guidance with an example ('Use when: create a collection called...') and an explicit exclusion with alternative ('Don't use when: the collection may already exist — check with zotero_list_collections first'). This is exactly the kind of when/when-not guidance expected.

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