Zotero Create Collection

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the create (write) behavior and the dual-acceptance of parent_collection (key or name, and explicitly not parent_key), which is useful behavioral context. However, it does not disclose success behavior, return value shape, duplicate-name handling, or error conditions. Since there is no annotation coverage, more behavioral disclosure would be warranted.

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 with no waste. The primary function is front-loaded, the subcollection edge case follows, and the pointer to find keys closes it out. Every clause earns its place without repetition or padding.

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 low-complexity (2 params, 1 required, no nested objects) and an output schema exists, so return-value documentation isn't the description's burden. The description covers the core behavior, the subcollection nuance with exact key format, and the key-lookup path. Minor gaps remain — duplicate-name handling and what the tool returns — but overall it's adequate for correct invocation.

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 — and it does. For parent_collection it adds significant meaning: what it's for (subcollections), accepted formats (key like 'KMMQDFQ4' or name), and the exclusion of parent_key. It also maps name to its purpose implicitly. This substantially exceeds what the bare schema provides, though it doesn't elaborate on formatting rules for name (e.g., uniqueness).

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 (create) and resource (collection), clarifies that 'collection' means project/folder, and distinguishes itself from siblings: this is create, not search (zotero_search_collections), not get (zotero_get_collections), not update/delete. The 'not parent_key' clarification adds precision. An agent can immediately tell this tool apart from its Zotero siblings.

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 gives explicit context on when to use parent_collection (for subcollections) and the exact accepted formats (8-character key or name). It also routes the agent to zotero_search_collections for finding collection keys. It doesn't explicitly state when NOT to use this tool versus update/delete, but the guidance provided is specific and actionable for the primary use case.

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