zotero_add_by_csl_json

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

With no annotations provided, the description carries the full burden. It discloses that the `id` field is stored in Extra as Citation Key and that an open-access PDF attachment is attempted for entries with a DOI. This adds useful behavioral context beyond the input schema, though it does not cover error handling or duplicate behavior.

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 four sentences long, each adding essential information. It front-loads the core purpose, follows with input constraints, then behavioral notes. No extraneous text; every sentence earns its place.

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?

Given the tool has 5 parameters (none required) and an output schema exists, the description covers the main input mechanism and notable side effects. However, it omits explanation for `tags`, `collections`, and `attach_mode`, which are common in Zotero workflows. A brief mention of these would complete the context.

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%. The description explains the mutual exclusivity and data types for `csl_json` and `file_path`, and hints at `attach_mode` implicitly via PDF attachment behavior. However, `tags`, `collections`, and `attach_mode` values (e.g., 'auto') are not explained, leaving the agent to rely solely on parameter names.

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 clearly states the verb ('Add'), the resource ('items to Zotero'), and the input format ('from CSL JSON'). Among siblings like zotero_add_by_bibtex, zotero_add_by_doi, etc., this tool is uniquely identified by its CSL JSON input, distinguishing it effectively.

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 instructs to provide EITHER `csl_json` OR `file_path`, not both, which is a key usage constraint. It also notes the preservation of the `id` field and PDF attachment behavior. However, it does not contrast this tool with siblings (e.g., when to prefer CSL JSON over BibTeX or DOI), leaving the agent to infer the context.

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