delete_bucket

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

With no annotations, the description carries full behavioral burden. It usefully discloses the destructive side effect that force purges contained objects before deletion, but says nothing about irreversibility, required permissions, or failure behavior on a non-empty bucket without force.

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?

A single front-loaded sentence with the destructive force behavior given inline. No waste, though the terse parenthetical could be expanded marginally for the missing details.

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 two-parameter tool with no annotations and no output schema, the description covers purpose and the force side effect but omits permission requirements and error/edge-case behavior, leaving gaps an agent would want before invoking a delete.

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 add meaning. It explains the force parameter's semantics (clear objects then delete), but the required bucket parameter is left entirely to the schema despite bare string typing.

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+resource (delete bucket) that an agent can distinguish from object-level siblings like delete_object. It does not, however, explicitly name an alternative or note that it operates on the whole bucket rather than its contents.

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 implies a use condition — force is needed to remove a non-empty bucket — which hints at when the option applies. There is no explicit when-to-use versus delete_objects_by_prefix or other cleanup alternatives, so guidance remains only implied.

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