Удаление S3-хранилища

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

The description discloses irreversibility and total data loss, which is essential behavioral context. However, the annotation destructiveHint is false, directly contradicting the description's statements that the action is irreversible and all data will be lost. Per rubric, any 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 three concise sentences, front-loaded with the primary action. Each sentence adds important information: the action, irreversibility, and the 2FA process. No redundant or filler content.

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 operational details: irreversible deletion, data loss, and the 2FA workflow. Since there is no output schema, the description carries the burden of explaining behavior, which it does adequately. However, it omits potential prerequisites like permissions or bucket state, and the annotation contradiction undermines trust.

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 covers 100% of parameters with descriptions. The description's 2FA flow is already reflected in the schema's descriptions for hash and code, so it adds minimal additional semantic value beyond what the schema provides. No new parameter details are introduced.

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: deleting an S3 bucket ('Удаляет S3-хранилище'). It uses a specific verb and resource, distinguishing it from sibling delete operations like delete_vpc or delete_balancer. The resource type is 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 specifies the two-step flow for accounts with 2FA, giving explicit sequencing guidance. However, it does not mention alternatives or conditions for when to avoid using this tool. The context is clear for a delete operation, but lacks exclusions.

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