Zotero Update Search Database

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

With no annotations, the description carries full burden. It discloses incremental vs full-rebuild behavior, performance expectations (seconds vs minutes), dependency requirements ([semantic] and configured provider), progress reporting via MCP context, and even the purpose of the limit parameter for smoke-testing. This is comprehensive behavioral disclosure.

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 front-loaded with the core purpose, then uses numbered scenarios for readability. Every sentence adds value—trigger conditions, cost trade-offs, dependencies, and an example. No fluff; it is long but efficiently organized for a tool with this complexity.

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 (semantic indexing, incremental vs full rebuild, dependencies, performance), the description covers all critical aspects: when to run, how it behaves, prerequisites, progress reporting, and a status-check sibling. It also provides an example call. Nothing essential is missing for correct invocation.

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 already covers both parameters with descriptions (100% coverage), so baseline is 3. The description adds operational meaning: force_rebuild is for changing models or corruption recovery, and limit is for smoke-testing. This extra context elevates it above the baseline.

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 a specific verb ('Build or refresh'), a resource ('semantic search embedding database'), and source ('from Zotero items'). It clearly distinguishes from siblings by naming zotero_get_search_database_status and implying semantic_search is the consumer, so an agent can route correctly without opening schemas.

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?

Explicitly lists three triggering conditions (first install, after zotero_add_item, after manual additions) and differentiates incremental vs force_rebuild with performance guidance. It also points to the sibling status tool for verification, leaving no ambiguity about when to call this versus alternatives.

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