search

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

No annotations exist; description mentions returns JSON with count and items list. Missing details on permissions, rate limits, or error behavior. Sufficient for a read operation.

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?

Well-structured with Args and Returns sections, using concise bullet points. No redundant info; every sentence serves a purpose.

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 optional parameters with no required inputs and an output schema present, the description covers all parameter behaviors and return shape comprehensively.

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 has 0% description coverage; description provides detailed semantics for all 7 parameters (e.g., tag: comma-separated AND search, itemtype: || operator). Adds substantial value beyond 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?

Description starts with 'Search the local Zotero library,' clearly stating the tool's action and scope. It distinguishes from siblings like get_item (single item retrieval) and search_semantic_scholar (external 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?

Each parameter includes usage instructions (e.g., 'Use || to combine types'). However, no explicit guidance on when to use this tool over siblings like search_semantic_scholar, or prerequisites.

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