Create Collection

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

Annotations already indicate this is a write operation (readOnlyHint=false) and not destructive (destructiveHint=false). The description adds context by specifying the library scope and the ability to nest under a parent collection via parent_collection_id, which is behavioral information beyond the annotations. This adds useful context about hierarchical organization.

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 two lines plus an argument list, front-loaded with the purpose. Every word earns its place; no fluff or repetition of schema details. It is highly concise and well-structured for quick parsing.

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 simple (two params, one required) and has an output schema, so the description need not explain return values. It covers the purpose and both parameters adequately, though it could possibly mention constraints like parent collection existence, but that is minor given the simplicity.

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 carries the full burden for parameter semantics. It explains both parameters: name as the collection name, and parent_collection_id as an optional parent key for nesting. This adds meaning beyond the raw schema types, though the explanations are brief.

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 uses a specific verb and resource: "Create a new collection in your Zotero library." It clearly states the action and the entity, distinguishing it from sibling tools like delete_collection or rename_collection. No ambiguity about what the tool does.

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 the use case (when you need to create a new collection) but does not explicitly state when to use it versus alternatives like add_to_collection or list_collections. No exclusions or alternative recommendations are provided, so guidance is only implicit.

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