reset

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

No annotations provided, so description carries full burden. It explicitly warns that the operation is permanent ('permanently removes all indexed documents and vector data') and destructive. However, it does not specify if other resources (e.g., settings) are affected.

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?

Extremely concise: two sentences plus a one-word warning line. Front-loaded with purpose, then warning, then usage instruction. No wasted words.

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 destructive tool with one parameter, the description adequately covers what the tool does and the safety requirement. It does not explain return values, but an output schema exists. Could mention effect on other tool operations.

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?

Schema has one boolean parameter 'confirm' with default false. Description adds meaning by stating 'Pass confirm=true to proceed', clarifying it is a safety gate. Schema description coverage is 0%, but description compensates.

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?

Clearly states 'Delete all documents and data (full factory reset)'. It uses a specific verb (delete) and resource (all documents/data), and distinguishes from siblings like 'remove' (single document) and 'settings_reset' (settings only).

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 this is for a complete reset but does not explicitly state when to use versus alternatives. It instructs to pass 'confirm=true' but lacks guidance on when not to use or mention of sibling tools.

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