List Zotero collections

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only behavior is covered. The description adds 'local' as scoping context but does not disclose additional behavioral traits such as pagination, sorting, hierarchy, or the shape of the returned data. It repeats 'Read-only' without adding beyond the annotations.

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 extremely short and front-loaded with the action and resource. However, the second sentence 'Read-only' largely duplicates the annotation metadata and the title, so it does not earn its place as fully as it could.

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?

This is a simple read-only listing tool with no required parameters, so the minimum invocation is clear. But with no output schema and no description of what the response contains or how pagination works, the description is not fully complete for an agent that needs to interpret the result.

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%, and the description does not mention the limit or start parameters or explain pagination behavior. The parameter names and numeric constraints are somewhat self-explanatory, but the description does not compensate for the missing schema descriptions as it should at this coverage level.

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 states a specific action ('List') applied to a clear resource ('local Zotero collections'). The 'local' qualifier and the tool name distinguish it from sibling tools like zotero_get_collection_items or zotero_search_items, so an agent can tell what this tool is for.

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 gives no explicit guidance on when to use this tool versus alternatives. It does not mention that zotero_get_collection_items should be used to fetch items inside a collection, nor any other routing information, leaving usage to be inferred from the name alone.

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