zotero_list_collections

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

With no annotations, the description carries the behavioral burden, but it only says 'List all collections', which conveys a read-only listing and an 'all' scope. It does not disclose whether nested collections are included, how results are returned, or that it operates on the current/default library.

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 sentence with no repetition, filler, or redundant detail. The key action and resource are front-loaded.

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, low-complexity tool, the description is mostly complete for selecting and invoking the call. It leaves minor gaps around library scope and return shape, but no parameters or output schema are present to contradict or complicate the basic behavior.

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 input schema has zero parameters, so there is no parameter semantics for the description to add; the rule for zero-parameter tools sets a baseline of 4. No additional parameter guidance is needed here.

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 uses a concrete verb ('List') with a clear resource ('all collections in the Zotero library'), making the operation unambiguous. It also distinguishes itself from sibling tools that operate on items, metadata, or search rather than listing 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?

No guidance is provided about when to use this tool versus alternatives such as zotero_get_collection_items or zotero_search. The description only states what it does, leaving the agent to infer selection context from the name.

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