zotero_add_by_bibtex

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

Given no annotations, the description carries full weight. It discloses support for multiple entries, preservation of citation keys in the Extra field, and attempted PDF attachment for DOIs. Missing details like duplicate checking or potential side effects on existing items.

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?

Three sentences, front-loaded with purpose, then usage constraint, then additional details. No unnecessary 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?

Adequate for basic usage but incomplete: explains only two parameters, lacks details on tags/collections/attach_mode, and does not mention return behavior (though output schema exists). For a tool with no annotations and five parameters, more detail is needed.

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 coverage is 0%, so description must compensate. It explains `bibtex` and `file_path` well. However, it omits `tags`, `attach_mode`, and `collections`, leaving three of five parameters undocumented despite their complexity (e.g., attach_mode default 'auto' not explained).

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 'Add one or more items to Zotero from BibTeX.' It specifies the action (add) and resource (Zotero from BibTeX), and distinguishes itself from sibling tools like zotero_add_by_doi and zotero_add_by_url by the input format.

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?

Provides explicit guidance: 'Provide EITHER `bibtex` (inline string) OR `file_path` (absolute path to a .bib / .bibtex file) — not both.' Also notes support for multiple entries and preservation of citation keys. However, it does not compare to alternatives or specify when to prefer this tool over other zotero_add_by_* tools.

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