arvan_s3_delete_bucket

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

The description adds the critical constraint that the bucket must be empty, which goes beyond the annotations (destructiveHint, idempotentHint). It does not, however, describe error behavior or return values.

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 extremely concise (5 words) and front-loaded. However, it sacrifices necessary detail about parameters and usage, making it somewhat under-specified despite its brevity.

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 1-parameter destructive tool with no output schema, the description covers the essential emptiness constraint. But it omits details like success/failure behavior, permission requirements, or what happens if the bucket is not empty.

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 sole parameter 'bucket' has no description in the schema (0% coverage) and the tool description does not elaborate on its expected format (e.g., name vs. ARN) or provide any context beyond the name.

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?

Description clearly states the action (Delete) and resource (bucket) with a specific condition (empty). This distinguishes it from other delete tools like arvan_s3_delete_object and arvan_s3_delete_objects which operate on objects, not buckets.

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 implies the tool is only for empty buckets but provides no explicit guidance on when to use it versus alternatives (e.g., emptying bucket first with delete_objects). No mention of prerequisites or side effects.

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