b2_delete_bucket

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

The description discloses the behavioral requirement that the bucket must be empty, which is a key runtime behavior. It doesn't repeat the destructive/idempotent hints already present in annotations, but the added empty-bucket condition goes beyond annotation info.

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 succinct and directly to the point, stating the action and one crucial precondition without any redundant wording. It effectively communicates the essential information in two short sentences.

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?

Given the simple nature of the operation and the presence of schema descriptions for parameters, the description adequately covers the core purpose and a key constraint. It doesn't explain return values, but no output schema exists, so that is not required.

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?

The description itself does not elaborate on parameters, but the schema descriptions cover 100% of the parameters (bucketId and confirm). Since schema coverage is high, a baseline of 3 applies, and the description adds no extra parameter meaning.

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 clearly states the action 'Delete' and the resource 'a B2 bucket', along with a necessary precondition. The verb and object are unambiguous, leaving no doubt about the tool's purpose.

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?

It provides a critical usage condition: the bucket must be empty before deletion. While it doesn't explicitly compare with alternative tools, the condition is highly informative for correct usage in typical scenarios.

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