zotero_collection_items

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive). The description adds behavioral detail beyond these: collection can be specified by key or reference, recursive mode includes nested subcollections, and duplicate items are removed. This goes beyond the annotations and gives the agent a precise expectation of output shaping.

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 entire description is a single concise sentence. It front-loads the action ('List items') and packs the critical optional behavior (recursive with dedup) without any filler. Every word adds value.

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?

An output schema exists, so return values are covered. The description provides the essential purpose, accepted identifiers, and the dedup/recursive behavior. The 'limit' parameter is a minor detail already constrained by schema (default 100, max 1000). For a read-only listing tool, this is complete.

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 only 25% (only key, name, path in the collection object are described; limit and recursive are not). The description partially compensates by explaining that 'collection' accepts a key/reference and hinting at the recursive option, but it does not explain the 'limit' parameter's behavior. It leaves a gap for a low-coverage 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 tool lists items in a Zotero collection, using specific identifiers (key or reference). It distinguishes itself from sibling tools like zotero_collections (which lists collections) and zotero_item_collections (which maps items to collections). The optional recursive behavior and dedup are also mentioned, 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 implies when to use the tool: whenever you need items for a known collection key/reference, with optional recursive traversal. It does not explicitly describe when not to use it or name alternatives, but the clear context of 'exact collection' and the sibling tool names provide sufficient guidance.

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