kb_reindex

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

No annotations are provided, so the description bears the full behavioral burden. It explains the trigger condition (external DB modification) but says nothing about cost, blocking behavior, whether the existing index is destroyed first, or whether the rebuild is safe to interrupt. For an index-rebuild maintenance operation, these are significant omissions.

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?

A single short sentence with no wasted words, and the trigger condition is front-loaded inside parentheses. It conveys exactly what the tool does and when to use it.

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?

With zero parameters, full schema coverage, and an output schema already present, the description does not need to explain return values or inputs. However, for a potentially expensive maintenance operation with no annotations, an agent would benefit from knowing about rebuild cost or lock behavior before invoking it.

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 tool takes zero parameters, which is the baseline-4 case. The empty input schema is consistent with the description, and there are no parameters whose meaning could be clarified further.

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?

States a specific verb and resource (rebuild full-text index), which is immediately distinguishable from sibling tools like kb_add, kb_search, or sqlite_query. It does not explicitly name siblings or explain the boundary, but the operation is unambiguous.

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 an explicit trigger condition: use after the database has been modified externally. This is clear context for when to invoke the tool. It stops short of stating when not to use it or naming alternatives, so it falls just short of a 5.

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