search_items

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds useful behavioral context beyond annotations by specifying that matching covers title, author, and tag, and that item_type and exact tags act as filters. 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?

The description is three short sentences with no filler. It front-loads the core action, follows with concrete usage triggers, and ends with filter semantics. Every sentence contributes.

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 read-only search tool with an output schema and clear annotations, the description supplies enough behavioral and parameter context to invoke it correctly. The main gap is not distinguishing this metadata search from search_fulltext, which would improve routing in ambiguous requests.

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 schema has 0% parameter description coverage, so the description carries the burden. It clarifies the meaning of the required query parameter, gives an item_type format example ('journalArticle', 'book'), and explicitly notes tag matching is exact. Pagination and response_format are left to self-explanatory names and the enum, so coverage is strong but not complete.

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 states a specific verb and resource ('Search Zotero library items by keyword') and clarifies the matching modes (title, author, tag). It does not explicitly name sibling tools like search_fulltext, so differentiation from them relies on the 'title/author/tag' qualifier, which prevents a 5.

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 explicitly states when to use it: 'when the user asks to find papers, look up references, or search their library.' It gives clear context but does not provide when-not-to-use guidance or mention alternatives such as search_fulltext, so it stops short of full exclusivity guidance.

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