list_collections

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

With no annotations provided, the description should carry the burden of behavioral disclosure. It indicates a read-style operation ('列出'), but does not explicitly mention read-only status, return format, pagination, or performance caveats beyond what the schema's parameter note mentions.

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 a single, concise sentence that front-loads the main purpose and includes only one additional relevant detail (optional counts). No wasted words.

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 low-complexity tool with one optional parameter and no required fields, the description is largely sufficient. However, it does not specify the return format or any usage caveats, which would be beneficial given the absence of an output schema.

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 100% with with_counts already explained ('是否统计条目数（较慢），默认 false'). The tool description adds no extra meaning beyond echoing this feature, so the baseline of 3 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 clearly states the tool's action and target: '列出 Zotero 全部 Collection（文件夹）' (list all Zotero Collections). It also adds an optional feature (item counts), distinguishing it from sibling tools like search_zotero_library or create_collection.

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 usage context is implied: it lists collections. However, there is no explicit guidance on when to prefer this over sibling tools (e.g., search_zotero_library, create_collection). No exclusions or alternative references are provided.

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