zotero_create_item

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 does disclose the key side effect (creating an item), the return value (the new item's key), and the 'empty item' behavior. However, it does not mention validation behavior, error conditions, whether the item is added to the library root by default, or any permission/context requirements.

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?

Three sentences with no filler. The purpose is front-loaded, then parameter usage, then a helpful cross-reference, then the return value. Every sentence contributes actionable 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 moderate complexity (4 params, one nested object, one required field) and the presence of an output schema, the description is quite complete. It explains the creation flow, valid field discovery, and return value. It could be slightly stronger by noting how collection_keys and tags interact with the creation, but the schema already names those parameters clearly.

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 covers all parameters, so the baseline is 3. The description adds meaningful value by clarifying that fields can be partially set, giving common examples of field names, and pointing to zotero_item_metadata for discovering valid fields per type. This goes beyond the schema's generic 'Fields to set' description.

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 clear action ('Create a new empty item in the library') with concrete examples of item types ('journalArticle, book, report, or webpage'). It also implies what makes this tool distinct from sibling creation tools like zotero_create_note or zotero_create_annotation, so an agent can select it appropriately.

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 practical usage guidance: pass only the fields you want set, and use zotero_item_metadata on an existing item to discover valid field names. It stops short of explicitly stating when to prefer this tool over alternatives or when not to use it, but the create-item purpose is clear enough for most selection scenarios.

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