List collections

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

Annotations already mark the operation as read-only, idempotent, and non-destructive, so the description's job is lighter. It meaningfully adds behavior details beyond that, such as the flat return shape with parentCollection keys, tree reconstruction in one call, and the distinction between root-level and child collections. No contradictions with annotations.

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 compact, front-loaded with the core purpose, and every sentence adds useful information. It explains scope semantics and cross-tool relevance without padding or repetition.

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?

Given the safe read-only annotations, a fully described input schema, and the presence of an output schema, the description covers the non-obvious parts: scope behavior, tree reconstruction, and key reuse by sibling tools. An agent has enough to select and call the tool correctly.

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%, so the schema already documents each parameter well. The description adds value by explaining the semantic effect of the scope values and clarifying that a parentCollection key is carried on each returned item, which helps agents understand how scope and parentKey interact.

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 'List collections in a library' and then details the three scope variants, so the core action and resource are unambiguous. It links returned keys to sibling tools like zotero_create_items, which helps place the tool in context, though it does not explicitly distinguish itself from zotero_get_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?

It provides concrete guidance for when to use each scope: 'all' for reconstructing the full tree, 'top' for root-level collections, and 'children' for direct subcollections of a parentKey. It also tells the agent that collection keys returned here are what several sibling tools consume, which is actionable routing information, though it stops short of explicitly naming when not to use this tool.

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