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

Annotations already establish readOnlyHint=true, idempotentHint=true and destructiveHint=false, but the description adds the critical non-obvious behavior: the tool 'opens nothing by itself' and only emits instructions, which reconciles the mutating-sounding name with the read-only annotation. The trailing sentence about Zotero's Web API v3 adds no behavioral value and reads as filler.

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 core behavior is front-loaded in the first two sentences, which is good. The final sentence about Zotero's public Web API v3, including a check date, does not help an agent select or invoke the tool and dilutes the message.

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 parameterless, instruction-returning tool with no output schema, the description covers what the agent gets back (step-by-step screens, buttons, fields) and what to do next. No return schema exists, so the description reasonably carries that load; only the API footnote is superfluous.

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, which is the baseline-4 case; there is nothing for the description to disambiguate beyond what the empty schema shows. The description does explain that item/collection selection is handled downstream by the browser tools, which is useful framing.

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 states a specific verb and resource ('Add to collection in the user's own Zotero account') and immediately qualifies it: the tool does not perform the action, it 'returns how to do it in Zotero step by step (screens, buttons, fields)'. That resolves the ambiguity in the name. It does not name any sibling Zotero tool (e.g. zotero_add_item_by_doi), so differentiation is only partial.

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 gives a clear follow-up path: after the steps are returned, perform them with the cotlet_browser_* tools in the Zotero Cloud Browser. However, it never says when to prefer this over the sibling Zotero tools that also modify library state, and gives no prerequisites or exclusions.

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