s3_delete_account

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

Annotations already mark the operation as destructive, but the description adds specific behavioral context: all buckets and data will be removed, and the operation requires HOSTKEY_ALLOW_DESTRUCTIVE=1. This is meaningful detail beyond the boolean annotations, though it stops short of discussing irreversibility or cancellation paths.

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 sentences with no filler. The destructive warning and environment requirement are front-loaded, making the most critical information immediately visible to the agent.

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 account-level operation with no output schema, the description covers the core consequence and required environment flag, and the schema fully documents parameters. The main gap is that it does not mention whether deletion can be undone or routed through s3_cancel_account_deletion, but this is not essential for invoking the tool 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 description coverage is 100%, so the parameter semantics baseline is 3. The description itself does not add parameter details, but the schema already documents that confirm must be true and account_id is optional with guidance to check s3_get_users.

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 operation: 'Полностью удалить S3-аккаунт пользователя' (completely delete the user's S3 account), with a specific verb and resource. It also identifies the underlying API operation (s3/delete_account) and implicitly distinguishes itself from sibling tools like s3_delete_bucket and s3_delete_file by targeting the account itself.

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 gives an important prerequisite (HOSTKEY_ALLOW_DESTRUCTIVE=1) and warns that all buckets and data will be deleted, which implies the tool is for full account removal. However, it does not explicitly state when to use this tool versus alternatives such as s3_delete_bucket or s3_cancel_account_deletion, nor does it mention any exclusions.

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