reset_index

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

With no annotations provided, the description fully carries the burden of disclosing behavior, and it does so clearly: the tool destroys all indexed documents and clears the persisted vector store. It does not explicitly mention irreversibility or downstream effects on search_context/index_info, but the destructive scope is explicitly and strongly stated.

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 a single, front-loaded sentence with no filler. Every word contributes to the agent's understanding of the tool's destructive effect.

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 zero-parameter destructive reset operation, the description is complete: it states exactly what is dropped and what is cleared, and the presence of an output schema covers return-value expectations. Sibling tool names provide enough surrounding context to situate this operation within the broader indexing workflow.

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 accepts zero parameters, so there is no parameter semantics burden on the description. The schema already trivially covers 100% of parameters, and the description adds a clear conceptual model of what the parameterless invocation accomplishes.

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 names a specific verb ('Drop') and resource ('every indexed document' and 'persisted vector store'), making the tool's destructive reset purpose unmistakable. It clearly distinguishes reset_index from siblings like index_document, search_context, and index_info, which operate on or query the index rather than clearing it.

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 wording strongly implies this is the full-reset tool: 'Drop every indexed document' is unambiguous. However, the description never explicitly states when to choose reset_index over alternatives, nor does it warn that this should not be used for selective deletions or before confirming the loss of all indexed data.

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