Delete Scaleway Object Storage bucket

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

Annotations already flag destructiveHint=true, but the description adds critical context beyond that: the deletion is permanent, the bucket must already be empty, confirm=true is mandatory, and the operation fails if objects exist. This significantly clarifies behavior and safety constraints, going well beyond the annotation.

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 a single, front-loaded sentence that conveys all critical information: permanence, the empty-bucket requirement, the confirm flag, and the failure mode. No unnecessary words or repetition.

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 deletion tool with rich annotations and a fully descriptive schema, the description covers the essential behavioral aspects (permanence, prerequisites, failure condition). No output schema is needed for a delete operation. The description is complete and helps the agent invoke the tool safely.

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% and each parameter has a descriptive comment. The description's mention of 'confirm=true' reinforces the confirm parameter but does not add new semantic meaning beyond the schema. With full schema coverage, 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?

The description clearly states the action: 'PERMANENTLY delete an empty Object Storage bucket.' The verb 'delete' is specific, the resource is identified, and the term 'empty' distinguishes this from tools that delete objects within a bucket. It also differentiates from sibling tools like scaleway_s3_delete_object, scaleway_s3_delete_bucket_tagging, etc.

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 provides clear context: the bucket must be empty, and confirm=true is required. It states a failure condition ('Fails if the bucket still contains objects'), which implicitly guides the user to empty the bucket first. However, it does not explicitly name alternatives like scaleway_s3_delete_objects or suggest a safe deletion workflow, so it falls short of a perfect 5.

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