clear_index

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

Discloses irreversibility ('Irreversible — all indexed metadata and search history is lost'), what is preserved (in-memory caches are not cleared), and the post-condition. No annotations provided, so the description fully bears the transparency burden.

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?

Four sentences, each adding value: action, use case, post-operation instruction, and distinction from sibling. Front-loaded with the main purpose.

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?

Despite no output schema or annotations, the description is fully self-contained: it explains the action, when to use, what is affected, what to do next, and what is not affected. Nothing essential is omitted.

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 has no parameters (100% coverage), so the description does not need to add parameter details. It correctly implies that no extra arguments are needed, earning a baseline of 4.

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 starts with a clear verb and resource: 'Delete the entire persistent SQLite mailbox index from disk.' It specifies the tool's sole purpose and distinguishes it from sibling tools like clear_cache.

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 states when to use ('Use only to reset a corrupted or schema-incompatible index') and what to do after ('After clearing, call sync_emails to rebuild'). It also contrasts with clear_cache for clearing in-memory caches.

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