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 of behavioral disclosure. It states the tool lists items, implying a read-only operation, but doesn't cover critical aspects like pagination (the 'limit' parameter suggests it), error handling (e.g., invalid collection_key), authentication needs, or rate limits. The description is minimal and leaves key behavioral traits unspecified.

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, clear sentence with zero wasted words. It's front-loaded with the core purpose ('List items in a specific Zotero collection'), making it easy to parse quickly. Every part of the sentence contributes directly to understanding the tool's function.

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 moderate complexity (2 parameters, no annotations, but with an output schema), the description is incomplete. It covers the basic purpose but lacks usage guidelines, parameter details, and behavioral context. The presence of an output schema means return values are documented elsewhere, reducing the burden, but the description still misses key operational aspects for effective use.

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 0%, so the description must compensate for undocumented parameters. It mentions 'a specific Zotero collection', which hints at the 'collection_key' parameter, but doesn't explain what a collection_key is or its format. The 'limit' parameter is not addressed at all. The description adds minimal semantic value beyond the schema's structural definition.

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 action ('List items') and resource ('in a specific Zotero collection'), making the purpose immediately understandable. It distinguishes from siblings like 'get_collections' (which lists collections) and 'get_item' (which retrieves a single item), though it doesn't explicitly name these alternatives. The description is specific but could be slightly more precise about what 'items' refers to (e.g., bibliographic entries).

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 description provides no guidance on when to use this tool versus alternatives. It doesn't mention when this tool is appropriate compared to 'search_items' (which might filter across collections) or 'get_item' (for single items), nor does it specify prerequisites like needing a valid collection_key. Usage context is implied but not articulated.

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