Удаление кластера базы данных

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

The description directly contradicts the annotation destructiveHint: false, as it says 'Удаляет' (deletes) and uses the DELETE HTTP method. This is a serious inconsistency that could mislead the agent about the tool's destructive nature. The 2FA explanation is helpful, but the contradiction forces a score of 1.

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 only two sentences, front-loaded with the core action and followed by the 2FA caveat. Every word adds value, and the structure is efficient.

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 primary action and the critical 2FA behavior, but with no output schema, it does not describe success/failure response details or the full impact of the deletion. The contradictory destructiveHint annotation also undermines completeness for an agent assessing risk.

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?

Although the schema covers all parameters (100%), the description adds inter-parameter semantics by explaining the two-step 2FA flow: the first response provides 'hash', which must then be sent along with 'code' on a repeat request. This clarifies how code and hash relate beyond their 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 clearly states the tool's function: 'Удаляет кластер баз данных' (Deletes a database cluster) and specifies the exact HTTP endpoint. This distinguishes it from sibling tools like get_database_cluster or update_database_cluster.

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 usage context and includes explicit 2FA handling instructions: for 2FA accounts, the first request returns a hash, and the agent must repeat the request with that hash and the authenticator code. It does not explicitly mention alternatives, but the action is unambiguous.

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