zotero_search

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

With no annotations, the description carries the full burden. It discloses search modes ('everything' includes full text), top_level_only behavior, and sort/direction options. However, it omits the 'start' pagination parameter and does not explicitly state the operation is read-only.

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-organized: a one-sentence purpose, a usage cue, and a compact Args list. Each parameter gets a concise line with examples, and there is no fluff.

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 (10 optional parameters) and lack of annotations, the description is quite thorough, covering search, filtering, sorting, and search modes. The missing 'start' parameter is a minor gap, and return values are presumably handled by the output schema.

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 zero parameter descriptions (0% coverage), so the description fully compensates by documenting 9 of 10 parameters with types, examples, and constraints. Only 'start' is missing, but the Args section adds substantial meaning beyond the bare schema.

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 'Search the Zotero library and return matching references' with a specific verb and resource. It clearly distinguishes from siblings like zotero_get_item by focusing on searching rather than single-item retrieval.

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?

It explicitly instructs to 'Use this before citing anything, to find the item keys that the Word tools need', giving clear when-to-use context. It also notes 'Leave empty to browse', but does not mention when not to use it or name alternatives.

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