s3_delete_account

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known; the description then adds substantive context: the blast radius ('all buckets and data will be deleted') and an environment-level authorization gate. It stops short of saying whether deletion is immediate vs scheduled or reversible, which matters given a cancel-deletion sibling exists.

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?

Three short sentences, front-loaded with the operation and API path, then the destructive warning, then the prerequisite. Every sentence carries distinct, actionable information with zero filler.

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 three-parameter destructive mutation with no output schema and full annotation coverage, the description supplies what the structured fields do not: blast radius and the destructive-gate requirement. The remaining gap is recoverability — nothing says whether the account can be restored or whether this blocks other operations while pending.

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%, including the s3uid omission rule, the confirm must-be-true rule, and the deprecated account_id alias, so the schema carries all parameter meaning. The description adds nothing parameter-specific, which is acceptable at full coverage but earns only the baseline.

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?

States a specific verb ('fully delete') and resource ('a user's S3 account') and even cites the underlying API path (s3/delete_account). The word 'fully' plus 'all buckets and data will be deleted' cleanly separates it from narrower siblings like s3_delete_bucket, s3_delete_payment_account, and s3_cancel_account_deletion.

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?

Gives a genuine precondition (HOSTKEY_ALLOW_DESTRUCTIVE=1 must be set), which is real usage guidance an agent needs before attempting the call. However, it never says when to prefer this over siblings such as s3_cancel_account_deletion or s3_delete_payment_account, so the routing decision is left to inference.

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