zotero_collection_items

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

With no annotations provided, the description carries the burden of behavioral disclosure. 'List' clearly signals a read-only operation, and '(local) name' hints that name resolution is limited to the local source, but it does not describe pagination, return format, or side effects. This is acceptable for a simple read tool but not richly transparent.

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 one efficient, front-loaded sentence with no filler. It states the action and the key selection mechanism immediately, earning its place without redundancy.

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?

The combination of description and fully documented schema is sufficient for basic invocation, but there is no output schema and the description does not characterize what kind of 'references' are returned. For a tool with five parameters and no return-type documentation, a bit more context about the result shape would improve completeness.

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 baseline is 3. The description adds value by clarifying that collection lookup can be by key or by 'local' name, which is a nuance not fully captured in the schema's 'Collection key or name' description. That extra scoping helps agents choose the right parameter value.

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', and a clear resource, 'the references in a collection', and adds the operational detail 'by collection key or (local) name'. This clearly distinguishes it from sibling tools like zotero_collections (which would list collections) and zotero_search (general searches).

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 usage is implied: use this tool when you need the references/items inside a specific collection. However, it does not explicitly say when not to use it or mention alternatives such as zotero_search or zotero_recent, so the agent must infer the choice from the purpose alone.

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