Export citations for selected items

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds useful behavioral context by specifying the exact citation formats produced, including APA 7th with hyperlinked DOIs, in-text parentheticals, BibTeX, and CSL-JSON.

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 compact, front-loaded with the core purpose, and organized clearly into Args and Returns. Every sentence contributes necessary information, with no filler or repetition.

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 two-parameter read-only tool with an output schema, this description is complete: it explains both parameters, gives valid style values, states the return purpose, and is consistent with the read-only annotations. No important calling-time information is missing.

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%, but the description fully compensates: item_keys is defined as one key or comma-separated keys, and style is defined with every supported value and its meaning. An agent can construct valid calls without needing additional external knowledge.

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 lead sentence 'Render one or more items as formatted citations' names a concrete action and resource, and the style list makes the purpose tangible. It does not explicitly differentiate from the sibling zotero_export_collection_bibliography, but the item_keys focus implies item-level rather than collection-level export.

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 clearly implies the tool is for producing ready-to-paste citations from specific item keys, and it enumerates style choices. However, it does not explicitly state when to prefer this over zotero_export_collection_bibliography or give any when-not-to-use guidance, leaving the alternative selection to inference.

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