zotero_create_item

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

No annotations are provided, so the description must carry the burden. It clearly states the primary behavior—creating a new reference—and gives examples of creators and fields, but it does not disclose any secondary behaviors such as whether it can create duplicates or whether authentication is required. This is adequate but sparse for an unannotated tool, scoring a 3.

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 opens with a single-sentence purpose, followed by a concise argument list. Each item in the list adds value with examples and cross-references, avoiding unnecessary verbosity. It is well-structured and front-loaded.

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?

With 7 parameters and a schema lacking descriptions, the description covers all parameters and points to sibling tools for dynamic enumerations. The existence of an output schema means return values are covered elsewhere. Given the complexity, this is fully complete.

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 has 0% description coverage, and the description fully compensates by explaining every parameter with concrete examples. For instance, it details the creator structure with both personal and institutional formats, gives date formats, and references zotero_item_type_template for valid field names. This provides far more meaning than the bare schema.

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 starts with a specific verb+resource: 'Create a new reference in the Zotero library.' This clearly distinguishes it from sibling tools like zotero_update_item and zotero_delete_item. The scope is unambiguous.

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 provides clear context for usage by listing required and optional parameters and pointing to companion tools: 'Call zotero_list_item_types to see all' and 'Use zotero_item_type_template to see which fields are valid.' However, it doesn't explicitly state when not to use this tool (e.g., for updates), making it a 4 rather than 5.

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