create_collection

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

With no annotations, the description carries the full burden. It discloses a key behavioral trait: if a collection with the same name already exists, it returns the existing key. However, it does not specify the return value for new collections, handling of invalid parent keys, or potential error conditions, leaving notable gaps.

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 a single clear sentence in Chinese, front-loaded with the action and including a meaningful edge case. No filler or redundancy.

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?

For a simple create tool, the description covers the core action and an important edge case. However, it does not specify the return value on successful creation (only for duplicates), nor provide context on how this tool fits with siblings or handles the optional parent parameter. Adequate but incomplete given no output schema.

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%, so the baseline is 3. The description adds minimal meaning beyond the schema, only indirectly referencing the 'name' parameter with '同名' (same name). It does not elaborate on the 'parent' parameter, but the schema already adequately describes both parameters.

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 the tool creates a Collection in Zotero, using a specific verb and resource. It also distinguishes itself by noting the idempotent behavior when a collection with the same name exists, which differentiates it from naive create tools and siblings like list_collections.

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 usage context through the idempotency note, suggesting it can be used to ensure a collection exists, but it does not explicitly state when to use this tool versus alternatives like list_collections or import_to_zotero. No exclusions or direct comparisons are provided.

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