List Zotero Collections

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

Annotations already disclose readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe, read-only operation. The description adds valuable behavioral context by specifying the return structure ('collections with their key, name, parent, and item count') and explaining scoping behavior with parent_collection_key. This exceeds what annotations alone convey.

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 well-structured with clear sections: purpose, args, returns, and examples. The first sentence is front-loaded with the core purpose. However, the args list largely duplicates schema information that is already exhaustive, adding mild redundancy. Still, the overall length is reasonable and scannable, so it earns a 4 rather than a 5.

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?

For a list operation with no output schema, the description is remarkably complete. It covers the core behavior, optional scoping, return fields, parameter usage, and exclusions. The examples give concrete context, and the explicit pointer to zotero_search_items for a different use case ties it into the sibling tool ecosystem. There are no significant gaps.

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 provides 100% coverage and detailed descriptions for all five parameters, so the baseline is 3. The description goes beyond the schema by adding example-driven semantics: 'what collections do I have?' -> top_level_only=true and 'list the subfolders inside my Putumayo collection' -> parent_collection_key. This helps an agent map natural language to parameter values, which is not in the schema.

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 and resource: 'List the collections (folders) in a Zotero library, optionally scoped to one parent collection.' It distinguishes itself from the sibling tool zotero_search_items in the 'Don't use when' example, making the purpose unambiguous.

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 explicit when-to-use guidance with concrete use cases: 'what collections do I have?' and 'list the subfolders inside my Putumayo collection.' It also gives a clear exclusion: 'Don't use when: you want the items inside a collection (use zotero_search_items with collection_key instead).' This is exactly the level of guidance expected.

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