list_collections

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

The description only outlines the return format. It lacks disclosure of behavioral traits such as potential large response size, authentication requirements, rate limits, or any side effects. Since no annotations are provided, the description carries the full burden, which is not met.

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 two sentences, straight to the point, with no extraneous information. It front-loads the purpose and lists the return fields clearly.

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?

While the description covers the basic purpose and output for a simple list tool, it omits context about potential pagination, filtering, or scope (e.g., 'all collections' for the user). The presence of an output schema reduces some burden, but usage guidance is missing.

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 has zero parameters and 100% schema coverage, so no parameter documentation is needed. Baseline score 4 is appropriate per the scoring guide.

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 explicitly states 'List all Zotero collections' with specific fields (keys, names, item counts). It clearly distinguishes from sibling tools like list_collection_items (which lists items within a collection) and search_library (which searches across items).

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?

No guidance is provided on when to use this tool versus other listing/searching tools. The description does not mention prerequisites, alternatives, or scenarios where it is appropriate or inappropriate.

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