s3_delete_payment_account

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

The description goes well beyond the destructiveHint annotation by specifying that an active service will have a completion date set and that HOSTKEY_ALLOW_DESTRUCTIVE=1 is required. This gives concrete behavioral context and safety-critical information beyond what annotations already declare.

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, each carrying necessary information: the action, the destructive consequence, and the required environment variable. The content is front-loaded with the purpose and immediately followed by the most critical safety warning.

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?

Given the annotations and schema already cover safety and parameters, the description adds the key behavioral consequence and the environment prerequisite. It does not explain the return value or whether the deletion can be canceled, but this is a relatively simple initiation operation and those details are not clearly necessary.

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 both confirm and account_id are already documented. The tool description does not add further parameter-specific meaning, but there was no need to compensate because the schema is sufficient. Baseline 3 is appropriate.

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 action (initiate deletion of an S3 account) and the mechanism (via billing service cancellation), which clearly separates it from a direct immediate delete. It is clear and specific, but it does not explicitly name sibling tools like s3_delete_account or s3_cancel_account_deletion to further differentiate 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 description implies this tool should be used when you want to initiate deletion through billing cancellation rather than doing it directly, and it gives a prerequisite (HOSTKEY_ALLOW_DESTRUCTIVE=1). However, it does not explicitly state when not to use it or point to any alternative sibling tools, so guidance is mostly implicit.

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