zotero_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 only states 'List collections' and parameter usage, without disclosing behavioral traits like authentication requirements, read-only nature, pagination, or rate limits. The description adds minimal behavioral context beyond the obvious.

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 two sentences, front-loaded with the core purpose 'List collections,' followed by a concise parameter instruction. Every word earns its place with no fluff.

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 tool's simplicity (one optional parameter, output schema present), the description is sufficiently complete. It covers the core function and parameter usage. The output schema handles return value documentation, so the description does not need to explain that. Some minor context like pagination could be added, but it is not critical.

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 no descriptions (coverage 0%), but the description compensates well by explaining the meaning of the parent parameter: passing a collection key lists subcollections, and omitting it lists top-level collections. This adds clear semantics beyond the schema's type-only specification.

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 tool lists collections, with a specific verb and resource. It also explains the optional parent parameter to list subcollections, distinguishing it from sibling tools like zotero_collection_items which list items in a 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?

The description does not provide any guidance on when to use this tool over alternatives. While it explains how to use the parent parameter, it lacks explicit when-to-use or when-not-to-use context relative to sibling tools.

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