Server-rendered bibliography (library items)

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

Beyond the readOnlyHint and openWorldHint annotations, the description adds meaningful behavioral context: server-side rendering, CSL output, the 150-item cap, XHTML return type, and the desktop vs Web API key nuance. No contradiction with annotations exists.

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 front-loaded with the core purpose and is appropriately dense with operational details. The parenthetical about desktop vs Web API is slightly complex, but all sentences earn their place and no filler is present.

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 read-only formatting endpoint with no output schema, it covers the return type, limits, style default, and sibling alternative well. The only material omission is the semantics of library_id/library_type, which keeps it from being 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 description adds useful semantics for style (examples and default), item_keys (library items, max 150), and mentions locale and linkwrap. However, library_id and library_type remain undocumented in both the schema and the description, leaving a gap for two of six parameters.

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 action ('Produce a formatted bibliography') and the precise resource ('items already in a Zotero library, rendered server-side by Zotero in a CSL style'). It also explicitly distinguishes itself from the sibling tool zotero_format_bibliography, leaving no ambiguity about scope.

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?

It provides explicit when-to-use guidance: this endpoint is for library items and is capped at 150 items. It also names the alternative (zotero_format_bibliography) for arbitrary CSL-JSON or non-library items, and notes the auth context difference between desktop and Web API.

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