reset_index

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

Without annotations, the description clearly states this is destructive, clears all indexed data from memory, optionally removes files from disk, and cannot be undone. This goes beyond schema and provides necessary warnings.

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 short paragraphs, no fluff, front-loaded with main action. The second paragraph repeats some info but adds necessary warning.

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 destructive tool with no annotations, the description explains the operation, its scope, side effects, and the parameters are fully documented in schema. Output schema covers return values. 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?

Input schema covers both parameters with descriptions. The tool description adds context around the optional file removal and confirmation but doesn't add substantial meaning beyond schema. Baseline 3 is appropriate.

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 ('Reset') and resource ('entire knowledge index'), and states what it does (clearing all indexed content). It clearly distinguishes from sibling tools like search or discover.

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 implies usage when you need to clear the entire index but doesn't explicitly state when to use it vs alternatives or when not to use it. It does mention destructive nature, which helps in decision-making.

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