Удалить базу или материал

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

Beyond the destructiveHint annotation, the description adds concrete behavioral details: deleting a base removes all its materials and vectors, and restoration is impossible. This gives the agent a clear and complete picture of the destructive consequences before invocation.

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 two short sentences: the first front-loads the core operation and conditional behavior, and the second delivers the critical irreversibility warning. There is no filler or repetition.

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?

Given the fully documented schema and the absence of an output schema, the description supplies the essential behavioral context: destructive scope, conditional operation, and irreversibility. No critical gaps remain for an agent to invoke this tool safely.

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 already documents all four parameters with descriptions, including the fact that omitting 'document' deletes the whole base. The description essentially restates this conditional behavior rather than adding new parameter-level meaning. Therefore, the high schema coverage keeps this at the baseline of 3.

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 clearly distinguishes the two deletion modes: one material when 'document' is provided, or the entire knowledge base with all materials and vectors when it is not. This makes the tool's purpose and scope immediately understandable and distinct from sibling knowledge tools.

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?

It gives explicit conditional usage guidance: include 'document' to delete a single material, omit it to delete the whole base. It also warns that deletion is irreversible, helping the agent weigh caution. It does not explicitly name alternatives, but no direct deletion alternative exists among the siblings, so this is adequate.

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