Batch-delete objects from Scaleway Object Storage

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

The description adds significant behavioral context beyond the annotations: it specifies permanence ('PERMANENTLY delete'), a batch limit (1000), a mandatory confirmation flag ('Requires confirm=true'), and clarifies it does not support recursive deletion. Annotations already set destructiveHint=true and idempotentHint=true, and the description aligns with and enriches these traits.

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 sentence with three concise clauses: purpose, requirement, and limitation. Every word adds value, and the key action ('PERMANENTLY delete') is front-loaded. No extraneous information.

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 batch delete tool with no output schema, the description covers all essential aspects: what it does (batch delete), how many (up to 1000), safety requirement (confirm=true), and what it does not do (no recursive). The sibling context and parameter descriptions fill remaining gaps, making this complete for agent invocation.

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 tool description itself does not describe parameters beyond noting the confirm requirement, which is already in the schema. However, the input schema has 100% coverage with detailed descriptions for all four parameters (e.g., keys: 'Explicit list of keys to delete...'). Per the rubric, when schema coverage is high, a baseline 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 states 'PERMANENTLY delete up to 1000 explicitly-named objects in one call,' which is a specific verb (delete) and resource (objects). The title 'Batch-delete' and the explicit mention of 'No prefix/wildcard form' clearly distinguish this from the sibling 'scaleway_s3_delete_object' (singular delete) and from any recursive bucket deletion tool.

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 includes 'Requires confirm=true' as a usage requirement and states 'No prefix/wildcard form - never wipes a bucket recursively' as an exclusion. It implies batch use for multiple known keys, but does not explicitly mention when to prefer this over the singular delete tool. The parameter description for 'keys' gives additional guidance about listing first, but that is part of the schema.

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