search

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

No annotations are provided, so the description carries full burden. It describes search behavior, full-text support, filtering, and pagination. It does not explicitly state read-only or side effects, but these are implicit 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 well-structured with Args and Returns sections, no fluff. Each sentence adds value. It is concise yet comprehensive.

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 7 diverse parameters and no required ones, the description provides complete documentation. It mentions return format (JSON with count and items). The output schema exists but is not shown; the description covers return structure sufficiently.

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 the description must compensate. It explains all 7 parameters with clear semantics, including defaults and usage examples (e.g., 'use || to combine types'). Adds significant meaning beyond the 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 starts with 'Search the local Zotero library', providing a clear verb and resource. It distinguishes from sibling tools like search_semantic_scholar (external search) and other specific tools.

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 details parameters and their usage, but does not explicitly state when to use this tool over alternatives. However, the mention of 'local Zotero library' implies context, and the comprehensive parameter descriptions guide usage.

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