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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, so the safety profile is covered. The description adds genuinely useful behavior beyond that: it explicitly says the tool 'opens nothing by itself' and only returns procedural steps, which is the single most important thing to know about this tool. The trailing note about Zotero's public Web API adds no operational value.

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, which is good, but the final sentence ('Zotero's official API: Zotero has a public Web API v3 with read and write access (checked 16 Oct 2026)') is irrelevant filler that does not help an agent select or invoke the tool. The first sentence's misleading framing could also be tightened.

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 guide tool with no output schema, it explains the flow and points to the follow-on browser tools. However, it never describes what the returned guidance looks like or what the agent must supply (e.g., a search term, collection, or field) to make the steps useful, leaving a gap.

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, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly implies it needs no inputs and simply returns guidance.

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 sentence frames the tool as 'Search library in the user's own Zotero account', which suggests an executing search, but the second sentence reveals it actually 'Returns how to do it in Zotero step by step ... and opens nothing by itself'. The true nature (an instruction/guide tool, not a search executor) is stated but is undercut by the leading verb and the title, so an agent could misread what it does on first pass.

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 clear workflow context: use this to get step-by-step guidance, then perform the action with the cotlet_browser_* tools in the user's Zotero Cloud Browser. No explicit when-not or sibling exclusions are given, but the sequencing advice is concrete and actionable.

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