Create a Scaleway Audit Trail export job

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

The description reveals critical behavioral traits beyond what annotations provide: 'creation triggers an IMMEDIATE backfill, not just a future cadence' with specific examples of the objects written. It also clarifies that delete_export_job does not clean up those objects, and that the bucket must be emptied manually before deletion. The permission requirements are explicitly stated. No contradictions 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?

The description is a single paragraph with multiple sentences, each serving a distinct purpose: purpose, prerequisite, behavioral caveat, permission guidance. It is reasonably concise given the amount of information packed in, but could be slightly more structured (e.g., bullet points for the caveats). No wasted words.

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?

Given the tool's complexity (7 parameters, no output schema, S3 integration), the description covers prerequisites, behavior, permissions, side effects, and related tools. It mentions checking job status via list_export_jobs but does not explicitly state what the create endpoint returns (e.g., job ID). This is a minor gap for a tool with no output schema.

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%, so the baseline is 3. The description adds some context for the bucket parameter (must exist, create it first) and mentions the prefix example, but this is already partially covered in the schema's parameter descriptions. The description does not add significant new meaning beyond what the schema provides for each parameter.

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 opens with a specific verb+resource: 'Create an export job shipping Audit Trail events to an Object Storage bucket (S3 destination).' This clearly distinguishes the tool from sibling audit tools like scaleway_audit_list_export_jobs and scaleway_audit_delete_export_job, and also references the prerequisite bucket creation tool (scaleway_s3_create_bucket).

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 explicitly states prerequisites ('The bucket must already exist and be writable - create it first'), when to use alternatives ('check last_run_at / last_status via scaleway_audit_list_export_jobs afterwards'), and error recovery ('if the call fails with permissions_denied, grant the Audit Trail write permission set via scaleway_iam_set_policy_rules'). It also warns about the side effect of the backfill not being undone by delete_export_job.

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