s3_delete_bucket

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is covered. The description adds the non-obvious constraint that only empty buckets can be deleted, but says nothing about the resulting error when a bucket is non-empty or whether the deletion is reversible.

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?

Four words with zero filler, and the key constraint ('empty') is front-loaded inside the phrase. It is terse to the point of under-specification rather than verbosity, so it loses a point on clarity.

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 operation with no annotations on failure behavior and no output schema, the definition is thin: it omits what happens on a non-empty bucket, whether the bucket must exist, and how errors are surfaced. The 'empty' precondition is the only substantive detail.

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 0%, so the description must carry the weight for the single 'bucket' parameter. It only implies that the parameter names the target bucket; there is no naming convention, format, required-state, or existence guidance to compensate for the empty schema.

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 and resource ('Delete ... bucket') and adds two useful qualifiers: the bucket is 'empty' and 'emulated S3'. The resource noun alone separates it from s3_delete_object, which targets objects, though no sibling is named explicitly.

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 word 'empty' implies a precondition (the bucket must contain no objects), which hints at when the call will succeed. It never states when to use this instead of alternatives such as deleting objects first, and gives no explicit exclusions.

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