Delete Scaleway Object Storage bucket

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

Adds key behavioral context beyond annotations: 'PERMANENTLY delete', 'immediate and irreversible', and the emptiness constraint. Annotations already flag destructiveHint=true, so no contradiction. The description reinforces the severity without repeating structured data.

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?

One concise sentence front-loaded with 'PERMANENTLY delete'. Every word serves a purpose with no extraneous content. The bold emphasis on 'PERMANENTLY' aids agent attention.

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 single-action tool, the description covers the core behavioral contract: irreversible deletion, emptiness prerequisite, and confirm requirement. No output schema exists, but return values are not critical for a delete operation. Slight gap: doesn't mention that the bucket name becomes available for reuse, but that is noted in the confirm parameter description.

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 coverage is 100% with detailed descriptions for each parameter (bucket, region, confirm). The tool description does not add new semantic info beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 verb 'delete' and the resource 'Object Storage bucket', with specific conditions (must be empty). Distinguishes from sibling tools like scaleway_s3_delete_object and scaleway_s3_create_bucket.

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?

Explicitly requires confirm=true and states the bucket must be empty. While it doesn't directly mention alternatives, the prerequisite (empty bucket) implies the need to first delete objects, guiding the agent away from premature use.

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