List Collections

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is well-covered. The description adds minimal behavioral context, mainly the scope 'in your Zotero library', which clarifies what data is accessed. It does not mention pagination, ordering, or whether it includes trashed collections, but with a strong annotation set and an output schema providing structure, this is adequate but not rich.

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, clear sentence with no unnecessary words. It is front-loaded with the key information and contains no redundancy or filler.

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 tool with no parameters, a clear scope, comprehensive annotations, and an output schema, the description is complete. It fully supports an agent in deciding to invoke this tool and understanding what it returns. No additional contextual details are necessary.

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, and the schema is empty. The baseline for 0 parameters is 4. The description does not need to explain parameters, and it doesn't. It clearly states what the tool does without needing parameter details.

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 is specific and clear: 'List all collections in your Zotero library.' It uses a precise verb ('List') and identifies the resource ('collections') and scope ('all... in your Zotero library'). It clearly distinguishes from sibling tools like get_collection_items (which lists items within a collection) and create_collection/delete_collection (which mutate collections).

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 description clearly indicates when to use this tool: when you need to see all collections in the library. It does not explicitly mention exclusions or alternatives, but the uniqueness of the 'listCollections' operation among siblings and the simplicity of the tool make the usage context obvious. There is no conflicting tool that does the same thing, so the lack of explicit alternatives is not a significant gap.

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