zotero_add_by_bibtex

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

With no annotations, the description fully discloses important behaviors: preservation of citation keys in the Extra field, automatic open-access PDF attempts for entries with DOIs, detailed `if_exists` handling, and validation of collection paths before creation. This goes beyond basic functionality.

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 a single paragraph that efficiently conveys key information without wasted words. It front-loads the primary action albeit with some density. A more structured layout (e.g., bullet points for parameters) could improve readability, but it remains concise.

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 7 parameters, no annotations, and an output schema exists, the description is sufficiently complete. It covers input constraints, behavioral details, and edge cases. The existence of an output schema compensates for the lack of return-value description.

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 description adds meaning to most parameters: the exclusivity of bibtex/file_path, the format of collections (keys, names, paths), the semantics of if_exists enum values, and the role of create_missing_collections. However, it does not explain `attach_mode` or `tags`, leaving gaps in parameter coverage.

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 tool adds items to Zotero from BibTeX, with specific verbs ('Add') and resources ('items to Zotero'). It distinguishes from sibling add tools by the source format (BibTeX vs CSL JSON, DOI, ISBN, URL, file).

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 explicit instructions on using either `bibtex` or `file_path` exclusively, explains the behavior of `collections`, `if_exists`, and `create_missing_collections`. It does not, however, explicitly exclude scenarios or mention alternative tools for similar tasks (e.g., using zotero_add_by_doi for a single DOI).

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