Delete a single object 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. The description adds the permanence emphasis ('PERMANENTLY') which goes beyond the generic destructive flag, and 'Requires confirm=true' highlights the safety gate. No contradiction with annotations; the schema further clarifies versioning nuance.

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?

Two short, front-loaded sentences deliver the essential message with zero fluff: what it does, the permanence, and the confirmation requirement. Every word earns its place.

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 simple single-object deletion tool with 100% schema coverage and rich annotations (destructive, idempotent, readOnly), the description plus schema is largely sufficient. It lacks explicit success/failure behavior, but the tool's simplicity and annotation coverage mitigate that gap.

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%, so the schema already fully documents all four parameters (key, bucket, region, confirm). The description adds no parameter-level detail beyond the schema; 'Requires confirm=true' merely restates the confirm constraint already present in the schema.

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 uses a specific verb+resource ('PERMANENTLY delete one object') and clearly distinguishes from the sibling tool scaleway_s3_delete_objects by specifying 'single object'. The title reinforces scope with 'Delete a single object from Scaleway Object Storage'.

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 phrase 'delete one object' implies this tool is for single-object deletion, but there is no explicit when/when-not guidance or mention of alternatives like scaleway_s3_delete_objects for bulk deletion. Usage context is only implied, not stated.

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