Build the semantic search index

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

The description discloses behavioral traits beyond annotations: it fetches library items, indexes text for BM25 and vector search, persists the index, and falls back to keyword-only search. Annotations only indicate readOnlyHint=false and openWorldHint=true, so the description adds significant value.

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 two sentences, front-loads the purpose, and efficiently covers all key aspects without extraneous detail. Every sentence earns its place.

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 has 3 parameters and no output schema, the description covers actions, indexing behavior, persistence, fallback, and usage timing. It lacks detailed explanation of library_id and library_type, but overall it is reasonably 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?

The description explains the 'action' parameter's enum values and their effects, but does not elaborate on the 'library_id' or 'library_type' parameters. With schema description coverage at 0%, the description partially compensates for the action param but leaves important library parameters undocumented.

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 builds, refreshes, or reports the status of a local hybrid-search index, distinguishing it from sibling tools like zotero_semantic_search. It identifies the specific verb-resource pair and enumerates the three actions (build, refresh, status).

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 explicitly says when to use the tool: 'Run a build before semantic searching, and refresh after large library changes.' It provides clear context but does not specify when not to use it or mention alternatives.

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