list_collection_items

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

With no annotations provided, the description carries full burden for behavioral disclosure. It transparently explains the limit parameter behavior (capped at 25, limit=0 returns empty, response metadata for clamping). It also details the return structure including 'collection_found', 'total', 'returned_count', and item fields. This goes beyond minimal expectations.

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-structured with a one-line summary followed by 'Args:' and 'Returns:' sections. While it is somewhat lengthy, every sentence adds value (parameter behavior, return fields). The most important information is front-loaded in the first sentence. A minor improvement would be tightening some phrasing, but overall it's effective.

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 exists and the tool has only 2 parameters, the description is remarkably complete. It covers the purpose, parameter details, and a comprehensive list of return fields including limit metadata and item structure. It anticipates potential questions (e.g., what 'total' means, what happens with limit=0) and addresses them. No gaps are apparent.

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?

For 'collection_key', the description adds crucial context: 'The Zotero collection key (from list_collections)' – the input schema only specifies type string, so this tells the agent where to obtain the key. For 'limit', the description reinforces the schema's explanation and adds the example of limit=0 returning empty, which aids understanding. Despite 50% schema description coverage, the description compensates effectively.

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 begins with a clear, specific verb+resource statement: 'List items in a specific Zotero collection.' This unambiguously states the tool's action and scope. It also implicitly distinguishes from siblings like 'list_collections' (which lists collections, not items) and 'search_library' (which searches across collections).

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 does not provide explicit guidance on when to use this tool versus alternatives. It does not mention that for items not belonging to a collection, 'search_library' would be appropriate, or that 'get_item' is for a single item. Usage context is only implied by the tool's purpose.

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