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 implies a read-only 'get' operation but does not disclose pagination, whether subcollections are included, what fields are returned, or how empty results are handled.

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 a single sentence with no filler and front-loads the core operation. It earns its place without redundancy, though it could add useful detail without losing conciseness.

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?

For a simple one-parameter read tool, the description captures the essential operation. However, it omits how collection_key is obtained, what the response looks like, and any limitations such as pagination or item-type handling. With no output schema and no annotations, the agent is left with some uncertainty.

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% because collection_key has a description ('Collection key'), so baseline 3 applies. The description itself adds no parameter meaning beyond the schema, and the schema's parameter documentation is terse.

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 states a clear action ('Get') and resource ('all items in a specific collection'), making the tool's purpose obvious. It is specific enough to distinguish from sibling tools like zotero_list_collections, though it does not explicitly name alternatives.

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?

No guidance is provided on when to use this tool versus zotero_search or zotero_list_collections. There is no mention of prerequisites such as obtaining a collection_key from zotero_list_collections, nor any exclusions or alternative routing.

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