s3_delete_account

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

Beyond the annotations, the description adds meaningful behavioral detail: 'все бакеты и данные будут удалены' (all buckets and data will be deleted) and the explicit requirement HOSTKEY_ALLOW_DESTRUCTIVE=1. This discloses the irreversible destruction scope and the environment gate, which the annotations alone do not convey.

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 short, front-loaded sentences. The first states the action, and the second delivers the critical destructive warning and prerequisite. The parenthetical endpoint reference is slightly redundant, but the overall structure is efficient and every sentence earns its place.

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 two-parameter tool with supporting annotations and full schema coverage, the description is complete: it names the action, states the irreversible consequence, gives the required environment flag, and the schema handles confirm and account_id. No output schema exists, but for a deletion operation the response format is not essential to invoking it correctly.

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 the baseline is 3. The description does not add parameter-specific meaning, but the schema already documents confirm as mandatory true and account_id as optional with guidance to check s3_get_users. The description's destructive warning reinforces why confirm is required, but adds no new parameter semantics.

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 and resource: 'Полностью удалить S3-аккаунт пользователя' (fully delete the user's S3 account), and clarifies scope by warning that all buckets and data will be removed. This is clearly distinct from sibling tools like s3_delete_bucket or s3_delete_file because the resource being acted on is the whole account.

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: it is for deleting an S3 account, and the destructive warning plus the HOSTKEY_ALLOW_DESTRUCTIVE=1 prerequisite provide clear context. However, it does not explicitly state when-not-to-use it or name alternatives such as s3_delete_bucket for bucket-only deletion or s3_cancel_account_deletion for cancellation.

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