Export a whole collection as a bibliography

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description does not contradict them. It adds useful constraints like the limit range and the return value, but it does not disclose any additional behavioral caveats such as pagination behavior or style-specific output differences.

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 and well structured: a leading sentence, a short Args block, and a Returns line. Every sentence adds information, and the most important scoping phrase appears first.

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 read-only export with an output schema and safe annotations, this description is complete enough to invoke correctly. Defaults are available in the schema, and the description supplies the remaining invocation-critical details.

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 carries the full burden for parameter meaning. It provides the collection key format, the exact allowed style values, and the 1-500 limit bound, all of which go beyond the bare input 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 opening line 'Render every item in a collection as a bibliography' names a specific action and resource with clear scope. It does not explicitly contrast with the sibling tool zotero_export_citations, so it stops short of full sibling differentiation.

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 gives no guidance about when to use this tool instead of alternatives such as zotero_export_citations, and it lists no exclusions or prerequisites. The intended use must be inferred from the name and title rather than from explicit usage direction.

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