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 burden. It discloses return fields and implies a read-only operation, but omits behavioral details such as pagination, result size limits, or how attachments are handled beyond the schema default. This is adequate but not thorough.

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 two sentences, front-loaded with the primary purpose, and includes return types and cross-references without extraneous detail. It is concise and well-structured.

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's simplicity (2 params, no output schema), the description covers the source of the collection key, the return content, and downstream steps. It lacks mention of pagination or nested items, but for typical usage it is sufficiently 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 100% for both parameters. The description adds value by indicating that collectionKey comes from get_collections, providing context beyond the schema's simple 'The collection key/ID'. It also implicitly references the excludeAttachments default by not contradicting it, though it doesn't elaborate.

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's function: 'Get all items in a specific Zotero collection' and enumerates the return fields (item keys, titles, authors, dates). It differentiates from sibling tools like get_items_details and get_collections by focusing on collection-level retrieval.

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?

Provides explicit workflow guidance: 'Use the collectionKey from get_collections' and 'Use the returned item keys with get_items_details, get_item_fulltext, or inject_citations.' This clearly indicates appropriate usage and downstream alternatives, though it does not explicitly mention when to prefer other tools like search_library.

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