Create collections

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

Beyond the annotations, the description discloses meaningful behavior: the 50-item per-call limit, the dependency that a child needs its parent's key so nested trees require one call per level, and that write authorization is handled automatically. This gives the agent practical expectations about batching and auth without relying on the schema or annotations.

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 compact and front-loaded: the core action comes first, followed by limits, nesting constraints, and authorization behavior. Every sentence adds useful information with no filler or repetition of the schema.

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 description is complete for a create-collection tool: it covers batch limits, nesting strategy, authorization requirements, and the core action. The output schema handles return-value expectations, so nothing critical is missing for an agent to select and invoke this tool correctly.

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 describes both parameters with 100% coverage, including the groupId behavior and the parentCollectionKey pattern. The description adds operational framing like 'up to 50 per call' and the nested-tree call strategy, but it does not significantly expand parameter-level meaning beyond what the schema already provides.

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 states a specific verb and resource: 'Create one or more collections,' with the additional nuance of optional nesting. This distinguishes it clearly from sibling tools like zotero_update_collection, zotero_delete_collection, and zotero_create_items.

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 clarifies when to use this tool for creating collections and provides important operational context: up to 50 per call, nested trees require a separate call per level, and zotero_authorize runs automatically. It does not explicitly name alternatives or state when not to use it, but the creation-specific wording makes the primary use case clear.

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