zotero_list_collection_items

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

With no annotations provided, the description carries the full behavioral burden. It discloses that only top-level items are returned and that child attachments/notes are excluded. It also implies a read-only review operation. It stops short of describing sorting or pagination behavior, but for a list operation the disclosed scope is meaningful.

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?

Two concise sentences, front-loaded with the action and resource, followed by a brief usage note and a key exclusion. Every sentence earns its place and there is no redundant content.

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 low-complexity list operation with a rich schema and an output schema present. The description covers the essential scope, use case, and important exclusion. Minor gaps like sorting or pagination behavior do not undermine correct invocation for the primary use case.

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 100%, so the schema already documents both parameters: collection_key and limit. The description adds no new parameter semantics beyond confirming the collection-key origin is known from zotero_list_collections, which appears in the schema anyway.

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 and resource: 'List the top-level items (works) in a collection.' It also specifies the returned fields (key, type, title, date) and explicitly excludes child attachments/notes, which distinguishes it from broader item-list or search tools.

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 a clear usage context: 'Use to review a collection's contents before moving items in or out.' It does not explicitly name alternatives or state when not to use it, but the intended scenario is clear enough to guide tool selection.

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