Rebuild the knowledge index to incorporate new files or changes to contextengine.json. Use after adding sources to refresh the operational context for AI agents.
Force a full re-index of all knowledge sources. Use after adding new files or changing contextengine.json.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v2.9.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description must disclose behavior. It states the action is a 'force' operation and affects all knowledge sources, implying potential resource intensity. However, it does not mention whether it is synchronous, reversible, or requires permissions. Adequate but not exhaustive.
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 concise sentences with zero wasted words. It is front-loaded with the action and immediately followed by usage context.
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?
For a simple tool with no parameters and no output schema, the description covers purpose and usage context. It could mention expected return or side effects (e.g., 'may take time'), but is largely complete given the tool's simplicity.
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 has zero parameters; schema coverage is trivially 100%. With no parameters, the description cannot add parameter-level meaning, but it does not need to. Baseline is 4 for zero-parameter tools.
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 uses a specific verb ('Force a full re-index') and clearly identifies the resource ('all knowledge sources'). It distinguishes itself from siblings, none of which describe re-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?
The description provides explicit context for when to use the tool: 'after adding new files or changing contextengine.json'. While it doesn't mention when not to use, the tool is singular in purpose with no clear alternatives among siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.