Create items

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

Beyond the annotations, the description discloses that Zotero validates each item independently and some items may succeed while others fail, which is essential behavioral context. It also explains the parentItem mechanism for notes and attachments. It does not discuss permissions or rate limits, but the annotations already cover the non-read-only, non-idempotent nature of the operation.

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?

Four tight sentences, each carrying distinct useful information: the batch limit, the collections optimization, the parentItem behavior, the attach_file alternative, and the failures guidance. The most important operational fact is front-loaded first.

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 sufficiently complete for this tool's complexity. It covers batch limits, partial failure behavior, collection filing, notes/attachments, and delegates file-disk attachment to the correct sibling tool. Since the output schema exists, the description need not re-explain the return values.

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 schema already documents all parameters at 100% coverage, so the baseline is 3. The description adds value by explaining that setting collections at creation time is cheaper than later movement, and that parentItem is the mechanism for creating notes and attachments. This goes beyond the raw schema descriptions.

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 opens with a specific verb and resource: 'Create up to 50 items in one call.' It clearly distinguishes this tool from the sibling update/delete/attach tools by describing the batch-creation action and the 50-item limit. It also clarifies that creating items is separate from file attachment, which is handled by zotero_attach_file.

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 concrete usage guidance: file items into collections at creation time because it is cheaper than moving them afterwards, and use zotero_attach_file instead when attaching a file from disk. It also directs the agent to inspect the returned failures array, which is practical advice for handling partial success.

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