zotero_bibliography

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states that entries are 'sorted alphabetically' and 'ready to paste into a document,' which conveys some output characteristics. However, it does not mention potential errors, the output format (e.g., plain text vs. HTML), or any side effects, so the transparency is moderate.

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 exceptionally concise: two sentences, 21 words. It front-loads the core purpose in the first sentence and adds a useful behavioral detail (sorting) in the second. There is no waste, repetition, or extraneous information.

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 2-parameter tool with no output schema, the description covers the basic purpose and one output trait (sorted entries). However, it omits important context such as what the returned bibliography looks like (e.g., plain text, HTML), the default citation style, and how the 'style' parameter affects output. Given the tool's moderate complexity, the description is adequate but 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?

The input schema fully describes both parameters ('keys' and 'style') with 100% coverage, so the baseline is 3. The description only references 'list of Zotero item keys,' which mirrors the 'keys' parameter but adds no additional nuance. It does not mention the 'style' parameter, its options, or the default, so no significant value is added 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 tool's function: 'Generate a formatted bibliography (Works Cited) from a list of Zotero item keys.' It uses a specific verb ('Generate') and resource ('bibliography'), and the phrase 'Works Cited' plus 'list of Zotero item keys' differentiates it from sibling tools like zotero_cite, which handle individual citations.

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 context for when to use the tool (when you have a list of Zotero item keys and need a bibliography), but it does not explicitly mention alternatives or when not to use it. Sibling tools like zotero_cite could be relevant alternatives, and the absence of any exclusion or comparison leaves the guidance implied rather than explicit.

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