zotero_list_collections

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

With no annotations, the description itself must carry behavioral disclosure. 'List all collections... as a tree' conveys a non-destructive, hierarchical read operation, and 'all collections' scopes the result set without filtering or pagination. It does not mention ordering or trash/group scope, but for a parameterless list the essential behavioral traits are present.

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?

Two concise sentences: the first front-loads the operation, output shape, and fields, while the second adds one practical next step. Every word earns its place, with no repetition of the tool name 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?

An output schema exists, so return-value details need no elaboration, and the description covers the tool's purpose and output shape well. It also provides the key linkage that returned keys are used by write tools. A brief note on scope exclusions (e.g., trash or group collections) would add even more completeness.

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 has zero parameters and the schema properties are empty, so there is nothing for the description to explain. The phrase 'all collections' appropriately confirms that no filtering inputs exist, matching the baseline for a zero-parameter tool.

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 opens with 'List all collections (folders) in the Zotero library as a tree,' which names a specific verb, resource, and output structure. It also lists the exact returned fields (key, name, parent, item count), clearly distinguishing it from siblings that operate on individual collections or items.

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 sentence 'Use these keys with the other write tools to organize your library' explicitly connects this read-only listing to downstream write tools, which is practical usage guidance. It does not enumerate exclusions such as when to use list_collection_items instead, so it stops short of a 5.

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