Zotero Get Collection Items

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

There are no annotations, so the description carries the full behavioral burden. It discloses the three detail levels, the presence of PDF/notes indicators, the subcollection expansion behavior, and the pagination convention where 'the response names the next offset to pass.' This is rich, concrete behavioral information that goes well beyond the input schema.

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 well-organized, front-loading the core purpose before covering options, pagination, and a routing tip. Every sentence adds information, and the TIP earns its place by pointing to a faster sibling tool. No redundant or verbose language is used.

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?

Given the tool has an output schema and moderately complex behavior, the description covers purpose, detail modes, subcollection semantics, paging, and the key alternative tool. An agent has everything needed to call this tool correctly without consulting additional documentation.

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 coverage is 80%, so the schema already documents most parameters. The description adds value beyond that by explaining the meaning of the detail enum values ('keys_only', 'summary', 'full'), the pagination naming convention for offset, and the practical consequence of include_subcollections. This is useful, though some parameter semantics are already present in the 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 opens with 'Get all items in a specific Zotero collection,' which is a specific verb-resource pair that clearly states the action and scope. It further distinguishes the tool from sibling search tools by describing its collection-based focus and by mentioning the alternative zotero_semantic_search for topic-based discovery.

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 TIP explicitly provides a when-not-to-use condition: for finding papers on a specific topic, use zotero_semantic_search instead, and gives the reason ('faster and returns only relevant results'). The description also clarifies the default subcollection behavior relative to Zotero's own 'Search subcollections' checkbox, giving agents clear context for when include_subcollections matters.

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