List Collections

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

No annotations are provided, so the description carries the full burden. It explains the hierarchical nature of collections and how parentKey filters results, but it does not clarify whether 'all collections' means all levels or just top-level, nor does it describe the return format, pagination, or sorting. This leaves some ambiguity about the tool's exact behavior.

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 three sentences long, front-loads the main purpose, and every sentence contributes useful information: the core action, the concept of collections, and the parameter usage. There is no unnecessary verbosity 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 simplicity of the tool (one optional parameter, no output schema), the description covers the essential purpose and the parameter's role. It could mention what happens with invalid parentKey or whether all collections are returned by default, but the current explanation is adequate for most use cases.

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 already describes parentKey as 'Parent collection key to list only sub-collections', and the description largely repeats this with 'Use parentKey to list sub-collections'. With 100% schema description coverage, the description adds minimal new meaning beyond the schema, warranting the baseline score of 3.

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 verb 'list' and the resource 'collections', and specifies the scope 'in the Zotero library'. It differentiates from sibling tools like create_collection, update_collection, and get_collection_items by focusing on collections themselves, and the added note about parentKey clarifies a distinct sub-use.

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 provides a clear context: 'Use parentKey to list sub-collections of a specific collection', which serves as a direct usage guideline. It does not explicitly mention when not to use this tool or suggest alternatives, but the context is clear enough for a simple list operation.

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