Reset Knowledge Base

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=true. The description adds the scope of the destructive action ('all documents'), but does not provide extra behavioral context such as irreversibility, whether the knowledge base remains, or any side effects. No contradiction with annotations exists.

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 concise sentence, front-loaded with the action, and contains no filler or redundant information. It earns its place without being verbose.

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, one-parameter destructive tool with complete schema coverage and annotations indicating destructive behavior, the description is largely sufficient for an agent to select and invoke it. A short note about permanence or that the KB itself is not deleted would make it fully complete.

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 input schema provides 100% coverage for the single parameter rag_id, described as 'Knowledge base id'. The description adds no additional parameter-level meaning, but also does not need to compensate for schema gaps.

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 and resource: 'Clear all documents from a knowledge base.' This clearly indicates the action and scope, distinguishing it from sibling tools like deleting individual documents or deleting the whole knowledge base. However, it does not explicitly name alternatives, so it falls short of a 5.

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 no guidance on when to use this tool versus alternatives like lyzr_kb_delete_docs, lyzr_kb_bulk_delete, or lyzr_kb_delete. There is no mention of prerequisites, context, or warnings about destructive consequences.

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