Create a Scaleway Audit Trail export job

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

The description goes far beyond annotations by revealing immediate backfill behavior, non-deletion of objects by delete_export_job, and the need for bucket cleanup. It also includes a live-verified date and troubleshooting for permissions_denied, providing strong operational context.

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?

Six sentences, each carrying distinct, high-value information including purpose, prerequisites, side effects, and permissions. Slightly long but every sentence is necessary; front-loaded with the core action.

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 mutation tool with 8 parameters and no output schema, the description comprehensively covers preconditions, side effects, monitoring, and permission requirements. It also references related tools for bucket creation and job deletion, giving a complete operational picture.

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?

Input schema covers 100% of parameters with descriptions; the description mostly reiterates bucket and confirm semantics already present in the schema. It adds no new parameter-level details beyond what the schema provides.

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?

Clearly states the tool creates an export job for Audit Trail events to an S3-compatible Object Storage bucket. The verb 'create' and resource 'export job' are specific, and it differentiates from sibling delete/list export job tools by describing the shipping destination.

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?

Provides explicit prerequisites (bucket must exist and be writable), a required confirm=true, and post-creation monitoring via scaleway_audit_list_export_jobs. It also mentions the permission boundary (read-only covers only query tools) and a remediation step, making it clear when this tool is appropriate.

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