zotero_search_items

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

No annotations are provided, so the description carries the full burden. It discloses that the tool searches and returns item keys, and describes two search modes. However, it does not explicitly state that the operation is read-only (implied but not confirmed), nor does it mention any rate limits or other behavioral traits.

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?

Two sentences with clear front-loading. Every sentence adds value: first states purpose, second explains modes and follow-up. 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 search tool with an output schema, the description covers the primary purpose and usage. It explains two qmodes and directs to related tools. However, it omits details about default item_type (excludes attachments) and pagination via limit, which would help completeness given the 5 parameters.

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 description must compensate. It adds value by explaining qmode options ('titleCreatorYear' default vs. 'everything') and the return type (item keys). But it does not describe the purpose of item_type, limit, or tag parameters, leaving gaps for a 5-parameter tool.

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?

Description clearly states it searches a reference library by keyword and specifies the resource type (papers, articles, books, notes). It connects to sibling tools by mentioning item keys for get_item_metadata or get_item_children. However, it could more explicitly differentiate from zotero_search_annotations, which searches annotations.

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?

Provides clear guidance on when to use default vs. 'everything' qmode, explaining that default searches title/author/year while 'everything' searches full text and note contents. Also informs the agent about subsequent tools to use (get_item_metadata or get_item_children). Does not explicitly state when to avoid this tool in favor of others like list tools.

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