list_zotero_items

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

No annotations are provided, so the description must carry the behavioral burden. It states the tool returns specific fields and implies a read-only listing, but does not explicitly confirm it has no side effects, nor does it describe pagination, error behavior, or rate limits.

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 extremely concise, using two short paragraphs. The purpose is front-loaded, and every sentence adds value without redundancy.

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 simplicity (one optional parameter, no annotations, and an output schema), the description adequately covers the purpose and parameter. It could add information about output format beyond the mentioned fields, but the presence of an output schema reduces the need.

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 input schema has 0% description coverage, so the description must explain parameters. It clearly documents the limit parameter with its default value (50) and meaning ('最多返回条目数'), adding value 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 explicitly states '列出 Zotero 库中的文献条目' (list literature items in Zotero library) and enumerates returned fields (itemID, key, title, PDF attachment ID). It distinguishes the tool's role as a discovery mechanism for item IDs, clearly differentiating from the sibling search_zotero_items.

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 mentions the tool is used 'for discovering item_id for other tools,' providing a specific use case. However, it lacks explicit guidance on when to prefer this over search_zotero_items, when not to use it, or any prerequisites or edge conditions.

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