b2_delete_bucket

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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description adds the key behavioral constraint that the bucket must be empty before deletion, which is not encoded in the annotations or schema. It does not discuss irreversibility in prose, but the schema's confirm parameter already covers that aspect.

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?

The description is two short sentences with no filler. The core action and the essential precondition are stated directly and upfront, making it easy for an agent to parse.

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 destructive tool with full schema coverage and destructive annotations, the description includes the one non-obvious operational requirement: the bucket must be empty. It does not describe the failure mode for a non-empty bucket, but that is reasonably inferable from the stated precondition.

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 bucketId and confirm thoroughly. The description adds no parameter-level meaning beyond the empty-bucket precondition, which is an operation-level constraint rather than a parameter detail.

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 opens with a specific verb and resource: 'Delete a B2 bucket.' It also adds the critical prerequisite about emptiness, which helps an agent understand the operation's scope and distinguishes it from siblings like b2_update_bucket or b2_delete_key.

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 clearly states when the tool is usable: only when the bucket is empty, and it explicitly says files and file versions must be deleted first. It does not name alternative tools or say when to prefer them, but the precondition provides meaningful usage guidance.

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