List the items in a collection

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering safety. The description adds the limit range (1-200) and the Markdown return format, which is useful context. But it does not describe pagination, ordering, or any side effects beyond what annotations imply. This is adequate but not rich.

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 compact and well-structured with clear Args and Returns sections. It front-loads the purpose and avoids redundant fluff. Every sentence contributes to understanding the tool.

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 simple read-only nature and annotations covering safety, the description is largely complete. It explains the return format and parameter semantics. Since an output schema exists (though not shown), the description need not elaborate further. Minor gaps like pagination details are acceptable for a listing tool.

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 coverage is 0%, so the description fully compensates by explaining both parameters: collection_key is an eight-character key sourced from zotero_list_collections, and limit has a 1-200 range with a default. This adds essential meaning beyond the bare schema definitions.

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 a specific action ('List the items held in one collection') and clearly distinguishes from siblings like zotero_list_collections (which lists collections) and zotero_get_item (single item). The return format is also mentioned, making the purpose unambiguous.

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?

Implies usage by requiring a collection_key from zotero_list_collections, which is a helpful prerequisite hint. However, it does not explicitly compare with alternatives like zotero_search or zotero_get_children, nor does it state when not to use this tool. The guidance is present but not fully developed.

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