Get Zotero collection items

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the useful 'top-level' behavioral detail, but it does not disclose pagination behavior, default limits, or what fields are returned.

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, with no redundant words, and the core action is front-loaded in the first sentence. Every part contributes to understanding what the tool does.

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 simple read-only list tool, this is minimally adequate, especially with annotations covering safety. However, there is no output schema and the description does not describe pagination behavior, return format, or when to prefer sibling search/list tools, leaving gaps for an agent fully autonomously using the tool.

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 explain collectionKey, limit, start, or how they interact. The schema's property names and constraints provide some hints, but the description itself adds no parameter-level meaning, which is required when schema coverage is this low.

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 uses a specific verb ('List'), a clear resource ('top-level items in a Zotero collection'), and adds scope ('top-level'). This clearly differentiates it from siblings like zotero_get_item, zotero_search_items, and zotero_list_collections.

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 guidance on when to choose this tool over alternatives. It does not mention that zotero_search_items should be used for searching across collections or that zotero_get_item is for fetching a single item's details.

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