Batch-delete objects from Scaleway Object Storage

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

Annotations already declare destructiveHint=true and readOnlyHint=false, lowering the bar. The description adds meaningful context: 'PERMANENTLY delete', 'immediate and irreversible' in the confirm param, and the reassuring guarantee 'never wipes a bucket recursively'. It does not discuss error/partial-failure behavior, but the safety-critical aspects are well covered.

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, dense sentence where every segment earns its place: permanence, batch limit, key-explicitness, confirm requirement, and anti-recursion safety. It is appropriately front-loaded and free of filler.

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 batch delete with 4 parameters and no output schema, the description covers the key operational constraints: key-count limit, no wildcard, confirm requirement, and the irreversibility. A small gap is the lack of guidance on partial failure behavior, but the main usage and safety context is complete.

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% and the schema descriptions are rich: keys mentions S3's hard cap, credits the no-wildcard form, points to list_objects, region states its default, and confirm explains irreversibility. The tool description itself adds no extra parameter detail, but the schema does the heavy lifting well beyond simple type info.

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 states 'PERMANENTLY delete up to 1000 explicitly-named objects in one call' — a specific verb+resource+scope. It clearly differentiates from the sibling scaleway_s3_delete_object (singular) by emphasizing the batch limit of 1000 and explicit-key scoping.

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 gives explicit when-not conditions ('No prefix/wildcard form - never wipes a bucket recursively') and names the alternative workflow ('list scaleway_s3_list_objects first if you need to delete everything under a prefix'). This exactly satisfies the 'explicit when/when-not/alternatives' ideal, even if the singular sibling is not named.

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