Zotero Export Bibliography

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

With no annotations, the description carries the full burden, and it does so thoroughly: it discloses the 100-item cap, output format as markdown with numbered list vs fenced code block, credential-free local mode, and the CSL engine behavior. It also clarifies the precedence and fallback behavior when no keys or collection are provided.

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 dense but every sentence adds essential information: purpose, parameter behavior, output shape, execution modes, cap, and a concrete example. It is front-loaded with the core purpose and then flows logically through parameters to edge cases and usage guidance.

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?

The tool is moderate in complexity with four optional parameters.closeThe description covers output schema implications, parameter interactions, operational constraints, and even provides a full invocation example. An agent has everything needed to select and correctly call this tool without further inference.

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?

Although schema coverage is 100%, the description goes well beyond the schema by explaining that item_keys accepts a JSON list string, that item_keys takes precedence over collection_key, that style is ignored for bibtex, and by giving concrete style examples. This adds meaningful operational semantics that the schema alone does not convey.

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 opens with a specific verb ('Render') and resource ('formatted bibliography or in-text citations'), and explains the intended use case of dropping references into a manuscript. The output formats and modes are clearly named, fully distinguishing this export tool from the many sibling retrieval/manipulation tools.

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 specifies how to choose among item_keys, collection_key, and the active library, including precedence and the 100-item cap with a scoping recommendation for larger exports. It also notes when style is ignored ('bibtex') and that the tool works both locally and via the web API, giving an agent clear decision guidance.

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