zotero_list_collections

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

With no annotations, the description carries the full burden. It discloses the effect of parent_collection_key (top-level vs. sub-collections) and uses the verb 'List,' implying a non-mutating read. However, it does not explicitly state read-only behavior, permissions, or pagination details beyond the limit parameter. The output schema covers return structure, but behavioral details like whether results are sorted or limited are omitted.

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 appropriately concise. It opens with a one-sentence summary, followed by a clear parameter explanation. Every sentence adds value, with no redundancy or filler. The structure front-loads the main purpose and uses a standard docstring format.

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?

The tool is simple, the output schema is present, and the description covers the key hierarchical behavior. The 'limit' parameter is not semantically explained, but it is a common pagination parameter with a default. Given the low complexity and availability of an output schema, the description is nearly complete, though a brief note on limit behavior would fully round it out.

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 0%, so the description must compensate. It explains parent_collection_key meaningfully ('List sub-collections of this collection. Omit for top-level collections.'), but it does not explain the 'limit' parameter at all. The schema provides a type and default for limit, but no semantic meaning. Thus, the description only partially compensates for the lack of schema descriptions.

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 (folders) in the library.' This is a specific verb+resource combination that distinguishes it from sibling tools like zotero_list_tags or zotero_list_libraries. The parameter explanation for parent_collection_key further clarifies hierarchical behavior, leaving no ambiguity about what the tool does.

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 clear context for usage: to list collections, with optional parent_collection_key for sub-collections. It explains that omitting the parameter gives top-level collections, which serves as practical usage guidance. However, it does not explicitly mention when to prefer this over alternatives, but the tool's purpose is distinct enough.

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