Delete a Scaleway Audit Trail export job

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

Annotations already flag destructiveHint=true, but the description adds: 'PERMANENTLY delete', 'Stops future exports; objects already written to the destination bucket are NOT deleted by this call.' This goes beyond the annotation by clarifying the exact side effects and what persists. No contradiction with annotations.

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?

Three sentences, each essential. Front-loaded with the action word 'PERMANENTLY delete'. No wasted words; permissions and side effects are efficiently explained.

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 delete tool with clear parameters and annotations, the description covers: action, prerequisite (confirm), behavioral nuance (bucket objects untouched), and error recovery (permissions fix). No output schema needed.

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 the description adds context: region defaults to server's region, confirm must be true, export_job_id sourced from list_export_jobs. The confirm description repeats schema text but ties it together. Good value-add.

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 explicitly states 'PERMANENTLY delete an export job by ID,' using a specific verb and resource. It clearly distinguishes this delete operation from sibling Audit tools like list_export_jobs and create_export_job.

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 explains the prerequisite 'Requires confirm=true' and the permission requirement ('Needs more than AuditTrailReadOnly...'), including a fix for permission errors. While it doesn't explicitly state when to use (e.g., 'when you no longer need the job'), the purpose is self-evident and the guidelines cover critical success factors.

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