List Zotero library items

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and openness profile is covered. The description adds the paging trait ('Page through'), which is useful context, but says nothing about ordering, rate limits, or what paging cursor to use (that lives in the schema).

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?

A single front-loaded sentence with zero filler; the scope constraint (library vs. collection) is stated immediately.

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?

With an output schema present and annotations covering safety, the description only needs to convey purpose and scope, which it does. It is adequate, though a brief note on ordering or how it relates to search_zotero would make it fully self-sufficient.

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 100%, so limit, start, and collection_key are fully documented in the schema, including the next_start paging hint. The description's 'library or one collection' only loosely echoes collection_key, adding no syntax or format detail beyond the schema.

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 gives a specific verb ('Page through') and resource ('bibliographic items') plus scope ('in the library or in one collection'), which is clearer than the bare title. It doesn't explicitly contrast itself with search_zotero, so the sibling distinction is only implied by 'Page through' vs. search semantics.

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?

There is no statement of when to choose this over search_zotero or get_zotero_item, nor any exclusions or prerequisites. The enumeration/paging use case is only implied by the words 'Page through'.

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