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

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

Adds critical behavioral context beyond annotations: deleting the base removes all materials and vectors, and the operation is irreversible. This meaningfully complements the destructiveHint annotation and warns the agent about the severe consequence.

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?

Two concise, front-loaded sentences with no filler. Every word contributes to understanding the tool's behavior and risks.

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 destructive deletion tool, the description covers scope (single vs whole base), consequences (materials and vectors removed), and reversibility. Combined with the schema and annotations, it provides a complete picture without needing an output schema.

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 coverage is 100%, so baseline is 3. The description adds semantic value by explaining the conditional role of the document parameter: its presence vs absence changes the operation from single-item deletion to full-base deletion, which is not obvious from the schema alone.

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?

Description specifies the resource (knowledge base/material) and the exact behavior: with the document parameter it deletes one material, without it deletes the entire base. This clearly distinguishes it 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?

Provides clear conditional usage: presence of the document parameter leads to single-material deletion; absence leads to whole-base deletion. It doesn't explicitly name alternatives, but among siblings this is the only delete tool for knowledge items, so the context is sufficient.

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