zotero_advanced_search

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

Since no annotations are provided, the description carries the full burden. It discloses conditions format, operations, field examples, defaults (limit, sort, join_mode), and a nuanced date example. Missing only minor behavioral traits like error handling or behavior with empty conditions.

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 well-structured: starts with purpose, then usage guidance, then parameter details, and ends with an example. Every sentence adds value; no unnecessary fluff. Front-loaded with most important information.

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 complexity (5 parameters, one required) and the presence of an output schema, the description covers conditions format, operations, field list, defaults, and an example. It could mention pagination behavior or edge cases, but is largely complete.

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 100% with good descriptions. The description adds significant value: lists common fields, exhaustive operations, an example, and notes that conditions can be a JSON string. This goes beyond the schema, raising the score above baseline 3.

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: 'Advanced item search with multiple structured-field conditions joined by AND or OR.' It also distinguishes itself from sibling tools by specifying when to use each, e.g., 'For plain text use zotero_search_items; for tags use zotero_search_by_tag; for topic discovery use zotero_semantic_search.'

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?

Explicit instructions on when to use this tool vs alternatives: 'Use this when you need to filter by fields that zotero_search_items and zotero_search_by_tag can't express.' Also lists specific scenarios like date ranges and itemTypes.

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