zotero_add_item

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

No annotations are provided, so the description carries the full duty of behavioral disclosure, which it handles well. It explains idempotence for if_exists='file' (reuses, adds missing, never removes), failure semantics for unknown collection specs, attach_mode behaviors, and that the call fails in local-only mode. It doesn't over-promise on return values, but with an output schema present this is largely 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 dense and front-loaded with the core purpose and usage directive, followed by structured parameter guidance. It's long but every sentence carries meaningful information; the section breaks (Routing, collections, if_exists, attach_mode) aid scanning. Slightly wordy in places but well organized for a tool with 8 parameters.

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 complex 8-parameter, 6-enum mutation tool with an output schema and zero annotation coverage, the description is thorough. It covers routing per source type, edge behaviors (unknown collections fail, local-only failure, noisy ISBN), idempotence semantics, prerequisites, and the post-call step. It even provides a concrete example invocation. This is highly 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?

Schema description coverage is 0%, so the description must fully explain parameters — and it does. Every parameter (source, source_type, collections, create_missing_collections, if_exists, attach_mode, title, and the extensions tags) is described with concrete semantics and even value examples (e.g., collections=['9SU943GB'], if_exists='file'). It adds routing context and idempotence details far beyond the 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 states a specific verb+resource ('Add item(s) to Zotero') and enumerates every supported input source (DOI, URL, ISBN, BibTeX, CSL JSON, file). It explicitly says 'Use for every add this to Zotero request', making the tool's domain unmistakable and distinguishing it from the many read/search/update/delete sibling tools.

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 explicit routing rules per source type (doi→CrossRef, url→doi.org/arxiv.org vs bare webpage, isbn→noisy, file→DOI extraction) with guidance to resolve to a DOI first. It also names the follow-up tool (zotero_update_search_database) and notes the writable-library prerequisite, providing clear when-to-use and caveats.

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