rebuild_index

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

Discloses key behavior: returns immediately without blocking, and search results reflect changes after completion. No annotations provided, so description carries burden; it does so well for a simple async 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?

Three concise sentences, each providing essential information: action, blocking behavior, usage trigger, and effect. No superfluous text.

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 purpose, when to use, and async behavior. Lacks mention of idempotency or error conditions, but given simplicity and absence of output schema, completeness is adequate.

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?

No parameters exist; schema coverage is 100%. Description adds no parameter info, which is acceptable for a tool with zero inputs. Baseline score of 4 applies.

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 'Trigger an incremental index update' with a specific verb and resource. It distinguishes itself from sibling tools like search_project_docs or list_projects by focusing on background indexing.

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 says 'Run this after adding or updating documents,' providing clear usage context. Omits mention of when not to use or alternatives, but the sibling set does not offer a similar rebuild tool.

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