zotero_create_item

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

With no annotations provided, the description carries the behavioral disclosure burden. It discloses that this is a write operation, requires write access, syncs to the desktop app, and needs user consent. It could additionally mention duplicate-creation risk or failure behavior, but the key side effects and authorization requirements are covered.

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 two tight sentences with no filler. It front-loads the core action and then immediately provides the critical auth and consent guidance.

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 12-parameter create tool with no output schema and no annotations, the description covers the most important operational context: write access, user consent, and sync behavior. However, it does not describe return values, error handling, or how to select this tool over closely related sibling tools, leaving some gaps for an agent.

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 only 42%, so the description must compensate, but it adds no meaning for individual parameters beyond the schema. It does not explain how title, itemType, creators, or extraFields interact, and it leaves many parameters to the schema's sparse 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 states a clear action ('Save a new reference') and target resource (the user's Zotero library), and adds the useful context that it goes through the web API and syncs to the desktop app. It does not explicitly name sibling tools, but 'new reference' distinguishes it from update and note-adding operations.

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 concrete usage context: it requires a configured API key with write access and instructs the agent to ask the user before writing unless explicitly asked. It does not explicitly contrast this tool with alternatives like zotero_update_item or zotero_add_note, but the prerequisites and consent rule are clearly stated.

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