zotero_bibtex

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

With no annotations present, the description carries the full burden. It discloses a key behavioral trait: it tries Zotero's native BibTeX export first, then falls back to a built-in simplified generator. It also notes the output is a 'simplified' version suited for quick citations, which informs expectations about output completeness.

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 definition is short and front-loaded with the action. However, it duplicates the same information in Chinese and English, which is unnecessary when both audiences can be served by a single concise message; still, the overall length is acceptable and each sentence adds context.

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 simple tool with one parameter and an output schema, the description covers the core purpose and fallback behavior. Yet it omits practical details like key formats, how the output is returned, and when the fallback is triggered. Since annotations are absent and schema coverage is zero, the description is only minimally sufficient, not fully 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 compensate. It only indicates the tool works for 'one or more items,' loosely mirroring the item_keys array, but fails to define what an item key is, where to obtain it, or how invalid/duplicate keys are handled. This is a significant gap for a parameter that is both required and untyped beyond 'array of strings.'

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 and resource: 'Generate BibTeX for one or more items.' It also clarifies scope ('one or more') and distinguishes itself from sibling tools like zotero_item or zotero_search, none of which target citation generation. The mention of a simplified generator adds further specificity.

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?

Usage context is implied: it is for creating BibTeX citations, which none of the sibling tools do. However, the description does not explicitly say when to prefer this tool over alternatives or mention scenarios where it should not be used. There are no exclusions or conditions for use.

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