get_collection_items

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

Annotations already signal read-only, idempotent, and non-destructive behavior, so the description carries a lighter burden. However, it adds no detail about pagination behavior, default limits, or how 'all items' relates to the limit/offset parameters. There is no contradiction with the annotations.

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?

Two compact sentences with no filler. The core verb and resource are front-loaded, and the usage context appears in the second sentence. Efficient and easy to parse.

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?

The output schema and annotations cover the return shape and safety profile, but the description omits important invocation details such as pagination semantics, response_format options, and how this tool differs from search_items for filtered collection queries. It is adequate for the common folder-contents request but incomplete for nuanced parameter 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, but it only clarifies collection_key ('by its key'). limit, offset, and response_format are left entirely to schema names and defaults; the response_format enum values are not explained, and the phrase 'all items' can mislead given the default limit of 100.

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?

States the exact action ('List all items') and the specific resource ('a specific Zotero collection by its key'), plus user-facing context ('folder/collection'). This clearly distinguishes it from sibling tools like get_collections, which lists collections rather than items, and get_item, which targets a single item.

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?

Explicitly provides a usage trigger: 'Use this when the user wants to see what's in a particular folder/collection.' It does not mention when not to use it or point to alternatives like search_items for filtered searches, so it stops short of a full 5.

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