s3_delete_bucket

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

No annotations are provided, so the description carries full responsibility. It discloses critical behavioral traits: failure if any object remains, irreversibility, and safe-usage requirement (confirmation). These are essential for a destructive operation and go beyond what the schema alone provides.

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?

Every sentence adds value: the main action, a key operational constraint, irreversibility, usage restriction, and a required verification step. No fluff, front-loaded with the core purpose.

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 simple delete tool with full schema coverage and no output schema, the description adequately covers the essential behavior: what it does, when it fails, and safety requirements. It could mention permissions or post-deletion impact, but these are not critical for the tool's intended use.

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 parameters are already well-documented. The description reinforces that the bucket must be empty but does not add new syntax or format details beyond the schema. 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?

Description clearly states the specific action: 'Delete an EMPTY S3 bucket.' The verb 'Delete' and resource 'S3 bucket' are precise, and the emptiness requirement distinguishes it from s3_delete_object and s3_create_bucket.

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 context by noting it is 'Reserved for dangerous guard mode' and instructs to 'ALWAYS confirm with the user before calling.' This indicates when it should be used, but it does not explicitly name alternatives (e.g., using s3_delete_object to empty the bucket first), which would clarify the full workflow.

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