zotero_add_by_csl_json

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

With no annotations, the description fully carries the transparency burden. It explains key behaviors: preservation of id in Extra, DOI-based PDF attachment, collection validation, and if_exists modes. It does not mention rate limits, authentication, or error handling, but the core behavior is well-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 appropriately sized (~120 words) and front-loaded with the purpose. It packs essential information without excess verbiage. Minor improvement could be structuring with bullet points, but current form is adequate.

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's complexity (7 parameters, optional, with output schema), the description covers most behavioral aspects. The output schema is present, so return values are not required. The description missing details on handling invalid inputs or edge cases, but overall complete for an agent to use effectively.

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 compensate. It explains 5 of 7 parameters (csl_json, file_path, collections, if_exists, create_missing_collections) but misses tags and attach_mode. The mutually exclusive nature of csl_json and file_path is clearly stated, adding value 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 clearly states the action ('Add one or more items to Zotero from CSL JSON') with a specific resource and format. It distinguishes from sibling tools like zotero_add_by_doi or zotero_add_by_bibtex by explicitly mentioning CSL JSON as the input source.

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 clear guidance on parameter selection (EITHER csl_json OR file_path) and details the behavior of options like if_exists, collections, and create_missing_collections. However, it does not explicitly contrast with sibling tools or state when to use this tool over others, which would improve clarity.

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