Удаление Kubernetes-кластера

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

The description states 'Действие необратимо' (action is irreversible) and describes a deletion operation, while the annotation destructiveHint=false indicates the tool is non-destructive. This is a direct contradiction. The description also does not disclose additional behavioral traits beyond the 2FA steps, and the contradiction undermines the tool's transparency entirely.

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 consists of two concise sentences, front-loaded with the core purpose ('Удаляет Kubernetes-кластер'), followed by the critical irreversibility note and the 2FA flow. No redundant information is present.

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?

The description covers the essential deletion action and two-step 2FA process, but it does not explain the final response after successful deletion or what happens for accounts without 2FA. Combined with the annotation contradiction, the overall context is incomplete, though the core function is adequately addressed.

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 schema fully describes all parameters (100% coverage), but the description adds meaningful workflow context by explaining that for 2FA accounts, the first call returns a hash and the second call requires both hash and code. This clarifies the parameter interplay beyond the individual schema descriptions.

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 the specific verb 'Удаляет' (deletes) with resource 'Kubernetes-кластер' (Kubernetes cluster), clearly distinguishing it from sibling tools like delete_k8s_cluster_node or delete_k8s_node_group. The purpose is explicit and unambiguous.

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 usage for whole-cluster deletion and provides the 2FA conditional flow, but it does not explicitly compare against alternatives or state when not to use this tool. No exclusions or alternative tool references are given, making the guidance partly implicit.

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