s3_delete_payment_account

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's destructive warning is consistent. The description adds valuable context beyond annotations: it explains the mechanism (canceling the service in billing) and the concrete effect (setting a completion date on the active service), plus the environment variable requirement. This is meaningful behavioral disclosure.

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 sentences, each earning its place: the action, the destructive consequence, and the required environment variable. The destructive warning is front-loaded and prominent. No wasted words.

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 mutation tool with no output schema, the description covers the key operational facts: what it does, what happens to the service, and the required flag. It does not mention how to confirm the operation or what the response looks like, but the schema's required confirm parameter covers the confirmation aspect. The pointer to s3_get_users for account_id resolution is a useful contextual addition.

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 schema already documents both parameters. The description does not add parameter-level detail beyond what the schema provides, but it does mention that account_id may be required and points to s3_get_users for clarification, which is a small addition. Baseline 3 is appropriate given full schema coverage.

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 action: initiating deletion of an S3 account by canceling the service in billing. It names the specific endpoint (s3/delete_payment_account) and explicitly flags the operation as destructive, which distinguishes it from read-only sibling tools like s3_get_users or s3_get_buckets.

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 when to use it: when you need to delete an S3 account via billing cancellation. It does not explicitly name alternatives or exclusions, but the destructive flag and the mention of requiring HOSTKEY_ALLOW_DESTRUCTIVE=1 provide clear context. It could be improved by noting that s3_cancel_account_deletion is the way to undo this action.

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