zotero_search_items

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: it excludes attachments and limits results to 30. However, it doesn't cover important aspects like whether this is a read-only operation, error conditions, rate limits, or authentication needs, leaving gaps for a search tool.

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 a single, efficient sentence that front-loads the core purpose and includes key constraints. Every word earns its place with no redundancy or unnecessary details.

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 moderate complexity (search operation with constraints), no annotations, and an output schema (which reduces need to describe return values), the description is partially complete. It covers the search scope and limits but misses parameter details and broader behavioral context.

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 1 parameter with 0% description coverage, and the description doesn't explain the 'q' parameter's semantics. It mentions searching by author and title, but doesn't clarify how 'q' relates to this or what format it expects. The description fails to compensate for the low schema coverage.

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 the tool's purpose: searching items in a Zotero library by author and title. It specifies the resource (Zotero library) and action (search), but doesn't explicitly differentiate from sibling tools like 'zotero_get_item' or 'zotero_read_pdf' beyond mentioning it's a search operation.

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 implies usage context by stating it searches by author and title, excludes attachments, and returns up to 30 results. However, it doesn't provide explicit guidance on when to use this tool versus alternatives like 'zotero_get_item' or 'zotero_read_pdf', nor does it mention any exclusions or prerequisites.

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