zotero_get_collection_items

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

No annotations are provided, so the description carries the full burden. It accurately describes the three detail levels and the inclusion of PDF/notes indicators. It does not mention any side effects, but as a read-only operation, this is acceptable. No contradiction with annotations.

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: two sentences and a tip. It is front-loaded with the core purpose, then details, then usage advice. Every sentence adds value 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?

Given the output schema is present and parameters are well-documented, the description covers all necessary context. It differentiates from sibling tools and explains the detail parameter sufficiently. No gaps remain.

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?

The schema already describes all three parameters (67% coverage). The description adds value by explaining the meaning of each detail level ('keys_only' minimal, 'summary' default no abstracts, 'full' with abstracts) and the PDF/notes indicators, which are not in the schema. This enriches parameter understanding.

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 retrieves all items from a specific Zotero collection, with a specific verb ('Get') and resource. It differentiates from sibling tools, notably zotero_semantic_search, by providing a tip for topic-based search.

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?

Explicit guidance is given: the description advises using zotero_semantic_search for topic searches instead, establishing clear when-to-use and when-not-to-use context. No other usage tips are needed.

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