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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered. The description still earns credit by disclosing that the tool 'opens nothing by itself' and that the response is a step-by-step guide with screens, buttons, and fields. The closing sentence about Zotero's public Web API adds no behavioral value for this specific tool and is mild noise.

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 purpose and the no-side-effects caveat are front-loaded and easy to scan. The final sentence about the official API version and check date does not help an agent decide or call this tool, so the text is not fully waste-free.

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 zero-parameter, no-output-schema tool, the description covers the essentials: what comes back (ordered steps with UI details) and what does not happen (no action taken). Only minor questions remain, such as whether an authenticated Zotero session is required before the browser steps can be followed.

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 tool takes zero parameters and the schema is empty, so there is nothing for the description to clarify about argument meaning. Baseline 4 applies.

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 names the resource (citations in the user's own Zotero account) and clarifies the actual behavior: it returns step-by-step instructions rather than performing the export. That distinguishes it from action-oriented siblings like zotero_add_item_by_doi. The headline verb 'Export' is slightly at odds with the guide-only behavior, which costs it a point.

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 explicitly states the sequencing: call this to get the steps, then execute them with the cotlet_browser_* tools in the Zotero Cloud Browser. There are no explicit when-not conditions or named alternatives among the Zotero siblings, but the workflow context is clear enough to route correctly.

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