Удалить подключение к ИИ

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

Annotations already indicate destructiveHint=true, but the description adds specific behavioral details: deletion removes saved keys and is blocked while bots are using the service. This goes beyond the annotation's generic destructive flag, providing useful context about the tool's limits and consequences.

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 sentences, front-loaded with the primary action, and provides a key caution without redundancy. Every sentence adds value and is appropriately sized for the tool's complexity.

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 tool with annotations, the description covers the primary action, the scope of deletion (keys), and a critical constraint (dependent bots). It omits details like irreversibility, but the destructive annotation already implies this, and no output schema exists to complicate completeness.

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%, and both parameters have descriptive text (provider required, case optional with default behavior). The description does not add parameter-level information, so the baseline of 3 is appropriate.

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 states 'Удаляет подключение вместе с сохранёнными ключами' – a specific verb (deletes) and resource (AI connection) with added detail about keys. It clearly distinguishes from sibling tools like ai_save and ai_test by specifying deletion behavior.

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 clear context about when deletion will fail: 'Пока сервис используют боты, панель удалить его не даст — сначала отвяжите его от ботов.' It gives a conditional scenario and remedy, though it does not explicitly mention alternative tools or when to prefer other AI tools.

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