list_zotero_items

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

No annotations provided, so description must disclose behavior. It states the operation (list), return fields, and limit parameter. However, it does not mention pagination, ordering, authentication needs, or potential performance implications for large libraries.

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: 4 short sentences in Chinese. It front-loads the main action, lists returns, gives purpose, and explains the parameter. No wasted words.

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?

For a simple list tool with one optional parameter and an output schema, the description covers input and basic output. But it omits return format details, sorting, and error handling. Output schema exists but is not shown; description still incomplete on behavior.

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?

With 0% schema description coverage, the description explains the only parameter 'limit' with default 50 and meaning (max number of items returned). This compensates fully for the schema gap, though no other parameters exist.

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 it lists Zotero library entries and specifies returned fields (itemID, key, title, PDF attachment ID). It distinguishes itself from sibling 'search_zotero_items' by implying a full list with limit, not a search filter.

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 it is used to discover item_id for other tools, but lacks explicit guidance on when to use it versus alternatives like search_zotero_items. No when-not or exclusion criteria provided.

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