Cancels an S3 account deletion initiated through billing and restores the account to active status.
Cancel S3 service deletion initiated via billing and restore the account to active status (s3/cancel_payment_account_deletion).
| Name | Required | Description | Default |
|---|---|---|---|
| s3uid | No | S3 account UID; omit only if the token is bound to a single S3 account | |
| confirm | Yes | Must be true to run the operation. | |
| account_id | No | Deprecated alias for s3uid / get_users.id |
Changes observed during successful MCP inspections.
v1.0.8Input schema / properties / account_id / descriptionPrevious value: -"Deprecated alias for s3uid"New value: +"Deprecated alias for s3uid / get_users.id"v1.0.4Input schema / properties / account_id / descriptionPrevious value: -"S3 account ID (if required; check via s3_get_users)"New value: +"Deprecated alias for s3uid"Input schema / properties / s3uidAdded value: +{
+ "description": "S3 account UID; omit only if the token is bound to a single S3 account",
+ "type": [
+ "string",
+ "number"
+ ]
+}v1.0.3Input schema / properties / account_id / descriptionPrevious value: -"ID S3-аккаунта (если требуется; уточняйте через s3_get_users)"New value: +"S3 account ID (if required; check via s3_get_users)"v1.0.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is carried by structured data; the description consistently adds that the outcome is account restoration to active status. It does not mention the mandatory 'confirm' gate, authorization requirements, or whether an already-active account errors out.
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?
A single front-loaded sentence with the operation first and the effect second; no filler. The trailing API route in parentheses is traceability rather than agent-usable information, a minor non-value-adding element.
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, non-destructive mutation with full schema documentation and no output schema, the description covers what it does and the resulting state change, which is what an agent needs to select it. Only the confirm-required behavior and error conditions are left to the schema.
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%, with all three parameters (s3uid, confirm, account_id) documented in-schema including the deprecated alias and the omit-if-token-bound case. The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.
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+resource ('Cancel S3 service deletion') plus the resulting effect ('restore the account to active status'), which is more than the name alone conveys. It does not name the counterpart operations (s3_delete_account / s3_delete_payment_account), but the purpose is unambiguous against them.
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 clause 'initiated via billing' implicitly scopes when this tool applies (an S3 deletion that came through the billing path), which helps select it over other S3 teardown tools. However, there is no explicit when-to-use/when-not guidance or named alternative for deleting an account outright.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.