zotero_create_collection

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

No annotations are provided, so the description carries full burden. It indicates creation (a mutable operation) but does not disclose potential side effects such as duplicate handling, permission requirements, or confirmation prompts. The lack of behavioral detail is a significant gap.

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?

Two sentences, each serving a distinct purpose: first stating the tool's primary action, second providing subcollection guidance. No extraneous words; front-loaded with essential 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 tool's simplicity (2 params, output schema exists), the description covers basic usage but omits important context such as error handling for duplicate names, expected output structure, or whether subcollection keys must exist. It is adequate but could be more comprehensive.

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. It clarifies that 'parent_collection' can be a key or name, and that it is for subcollections. However, it does not explain that 'name' is required (though schema indicates), nor does it describe constraints on name length or uniqueness, leaving gaps.

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 'Create a new collection (project/folder) in your Zotero library,' with a specific verb and resource. It also mentions subcollection creation, but does not explicitly differentiate from siblings like 'zotero_delete_collection' or 'zotero_manage_collections', though it does reference 'zotero_search_collections' for finding keys.

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?

Guidance is provided on when to use parent_collection for subcollections and how to find collection keys using zotero_search_collections. However, it does not specify when not to use this tool (e.g., for managing existing collections) or mention alternatives beyond searching.

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