delete_bucket

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

With no annotations provided, the description carries the full disclosure burden. It conveys that the operation is destructive ('Delete') and discloses the most important behavioral constraint — the bucket must be empty — which implies failure or refusal on non-empty buckets. It omits error behavior, irreversibility details, and permission requirements, but the safety-critical trait is present.

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?

Six words with the verb front-loaded and the critical constraint embedded in the same sentence. There is zero wasted text; every element earns its place.

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 low-complexity, one-parameter tool with an output schema present, the description covers the core operation and the single biggest gotcha (empty-bucket requirement). However, with no annotations and no parameter-level documentation, details about failure behavior on non-empty buckets and how to resolve a valid bucket identifier are left to the agent's domain knowledge.

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 compensate for the undocumented 'bucket' parameter. It only restates that the parameter identifies the bucket to delete, adding no format, example, or pointer to list_buckets for obtaining valid values. The 'must be empty' clause describes a bucket state, not the parameter's meaning, so it adds little beyond what the schema property name already implies.

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 the verb (delete) and resource (bucket) directly, with the critical qualifier '(must be empty)' distinguishing it from delete_object, which targets objects within a bucket, and complementing create_bucket. An agent can tell this tool's scope at a glance without opening any sibling schema.

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 parenthetical '(must be empty)' communicates the key precondition for safe use, implying the agent should verify emptiness before calling. However, it does not explicitly name alternatives or the when-not-to path, such as using delete_object to empty the bucket first, so the routing guidance is implied rather than stated.

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