zotero_collections

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

No annotations are present, so the description carries the burden of indicating safety and side effects. The verb 'List' implies a read-only operation, but the description does not explicitly state that nothing is modified, nor does it mention any limits, ordering, or whether empty collections are included.

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 concise and front-loaded. The two sentences are parallel translations of the same clear statement, containing no filler or irrelevant details.

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 parameterless list operation with an output schema, the description is nearly complete. It fully communicates the tool's scope, though it could have added a brief note about the relationship to zotero_collection_items or the structure/nesting of collections.

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 empty schema is fully self-documenting on that front. The description adds useful semantic emphasis with '所有/all', clarifying that the tool returns every collection without filtering.

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 verb ('List') and resource ('all collections in the library'), and the bilingual phrasing reinforces the meaning. It is clearly distinguishable from sibling tools like zotero_tags, zotero_collection_items, and zotero_search.

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?

No guidance is provided about when to use this tool versus alternatives such as zotero_collection_items or zotero_tags. The description only states what the tool does, leaving the agent to infer the appropriate context.

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