collection_items

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Retrieve', implying a read operation, but does not mention any side effects, permissions, or constraints beyond what is implicit. This is minimal transparency.

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 concise with a single sentence that front-loads the key action. It is appropriately sized for a simple retrieval tool, though it sacrifices some informative context.

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 complexity (many optional parameters for filtering, sorting, etc.) and lack of annotations, the description is too minimal. It does not explain what a 'collection' refers to (e.g., Zotero collection) or how the filtering parameters relate to retrieval. The output schema exists, but the description still feels incomplete.

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 top-level parameter 'req' lacks a description (0% coverage per context), and the tool description adds no parameter information. While sub-fields in the schema have descriptions, the description does not compensate for the missing top-level parameter context, leaving an AI agent with incomplete guidance.

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 ('Retrieve') and the resource ('items in a collection'), providing a clear purpose. However, it does not differentiate from sibling tools like 'search_items' or 'collection_items_top', which may also retrieve items but with different scopes.

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 offers no guidance on when to use this tool versus alternatives. Given many sibling tools (e.g., 'search_items', 'collection_items_top'), explicit usage context is missing, making selection difficult for an AI agent.

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