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

The description usefully discloses that the tool 'opens nothing by itself' and returns screens/buttons/fields, which is consistent with the readOnlyHint=true and destructiveHint=false annotations and adds real context. Beyond that it offers no detail on return format, length, or failure modes, and the trailing note about Zotero's public Web API v3 is unrelated to this tool's behavior.

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?

Three sentences, but two clauses ('from ChatGPT, Claude or any AI agent' and 'Zotero's official API... checked 16 Oct 2026') carry no decision-relevant information. The most important fact — that it only returns instructions rather than data — is buried after a misleading title-mirroring opener.

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, read-only tool with no output schema, the essentials are present: what it returns (steps, screens, fields) and what to do next (cotlet_browser_* tools). It is nonetheless incomplete in that it does not clarify the split of responsibility with the existing Zotero data tools, leaving the agent unsure whether a real annotation fetch is possible at all.

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 schema takes zero parameters and has 100% coverage, so there is nothing for the description to disambiguate. The baseline for a no-parameter tool applies, with only a small deduction for not clarifying that no arguments are accepted at all.

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 'Get annotations in the user's own Zotero account' names a verb and resource, but the very next sentence reveals the tool does not actually retrieve annotations — it returns step-by-step instructions for doing it manually. That gap between name/lead sentence and real behavior leaves the purpose only partially resolved, requiring the agent to read the whole description to understand what comes back.

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 does state a follow-on path ('then do it with the cotlet_browser_* tools in the user's Zotero Cloud Browser'), which is useful routing. However, it never states when this tool should be chosen over the many concrete Zotero siblings such as zotero_search_library, nor any exclusion or precondition.

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