zotero_update_search_database

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

No annotations provided, but the description fully discloses behavioral traits: incremental vs full rebuild, progress reporting via MCP context, time estimates, and required dependencies (semantic, config). No contradictions.

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?

Concise 6-sentence description with clear sections: purpose, triggers, default behavior, parameter details, progress, dependencies, and example. Every sentence adds value without redundancy.

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?

Output schema exists, so no need to explain returns. Description covers all necessary aspects: when to run, incremental/full modes, parameter details, dependencies, and performance. Complete for the tool's complexity.

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%, so baseline is 3. The description adds value by explaining when force_rebuild is appropriate (changing model, recovery) and for limit it adds 'smoke-testing' context, slightly above the schema's description.

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: 'Build or refresh the semantic search embedding database from Zotero items.' It distinguishes from sibling tools like zotero_get_search_database_status (check status) and zotero_semantic_search (use the database) by specifying it is the update/build 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?

Explicit when-to-use scenarios are listed (a, b, c), default incremental behavior is noted as cheap, and force_rebuild usage is explained. The description mentions checking status with a sibling tool, providing clear context.

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