Create a Zotero item from supplied metadata

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

Annotations provide only basic flags (readOnlyHint=false, idempotentHint=false, destructiveHint=false), so the description carries the burden. It adds useful behavioral context: dry_run behavior ('Show the payload without writing'), the Zotero creator shape, and the return value ('new item key and its APA 7th rendering'). It stops short of discussing duplicate handling or side effects, but it discloses the key behavioral traits for a creation tool.

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 compact and well-structured with clear Args and Returns sections. Every sentence earns its place: purpose, usage condition, parameter explanations with a concrete creator example, and return value. No redundant or filler text.

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 tool with 3 parameters (1 required) and an output schema, the description covers all the essential information: when to use it, how to structure item_json, what collection_key and dry_run do, and what is returned. The 0% schema coverage is completely mitigated by the description's depth.

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 has 0% description coverage—parameters are only named, not explained. The description fully compensates: item_json is described with required keys and an example creator shape, collection_key is defined as 'Optional collection to file the item in,' and dry_run is explained as 'Show the payload without writing.' This is far beyond what the schema provides.

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 an item from a metadata object you supply directly.' This clearly states what the tool does and distinguishes it from zotero_add_by_doi by specifying it is for sources without a DOI. 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 explicitly says 'Use this for sources without a DOI, such as a thesis, a technical report or a dataset.' This gives a direct when-to-use rule and implicitly routes DOI-bearing sources to the sibling zotero_add_by_doi. It is concise and actionable.

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