Build semantic index

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

Describes the process: extracts, chunks, embeds. Notes automatic fallback to keyword-only if embedding model absent. Annotations indicate idempotent and not read-only, which aligns with building an index. No contradictions. Adds behavioral depth beyond annotations.

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?

Two substantial sentences front-load the core purpose and list parameter usage. Dense but efficient; every clause adds value. Could be broken into bullet points for clarity, but acceptable for the 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?

Covers selection, force, prune, keywordOnly modes, but omits library and enableFts parameters. Also does not explain the relationship to sibling calibre_semantic_search or what exactly the index enables. Adequate but not fully complete given 8 parameters and 0% schema coverage.

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?

Explains bookId, ids, query as required selectors, and covers keywordOnly, force, prune. However, two parameters (library, enableFts) are not mentioned in the description. With 0% schema coverage, this is a notable gap.

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?

Clearly states the tool builds a semantic index for specific books, using bookId, ids, or query, and explicitly distinguishes from full-library indexing. The verb 'build' and resource 'semantic index for specific books' is specific, and it sets scope boundaries.

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?

Provides guidance on when to re-run (after adding books), when to use force (unchanged books), and when to use prune (removed books). Mentions keywordOnly for zero-ML search. While no explicit alternatives to siblings, the description implies when to use this vs. searching (calibre_semantic_search).

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