Create Scaleway Object Storage bucket

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

Annotations already indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the creation aspect is clear. The description adds important caveats: the bucket is private by default, Object Lock at creation is silently ignored on Scaleway, and references configuration tools for subsequent setup. The one missing detail is whether the operation is idempotent or what happens if a bucket with the same name exists, but the context of 'create' and 'S3' implies non-idempotent.

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 three efficient sentences with no fluff. The first sentence states the core action and default visibility. The second sentence immediately points to configuration tools for further setup. The third sentence provides a critical caveat about Object Lock and the correct workflow. Every sentence adds value and is front-loaded with the essential 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?

Given the simple 2-parameter input schema (bucket name and region), no output schema, and rich annotation context, the description is complete. It covers default visibility, post-creation configuration workflow, and a platform-specific nuance about Object Lock. There is no meaningful gap for this tool's purpose.

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%, covering bucket and region. The description adds no extra parameter-level detail, but this is acceptable because the schema already documents the bucket naming (minLength: 3) and region default. The region description in schema includes a concrete example ('fr-par'). The description's mention of 'private by default' and 'Scaleway' adds platform-specific context that aids selection.

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 clearly states 'Create a new, empty Object Storage bucket, private by default.' This provides a specific verb (create), resource (Object Storage bucket), and key attribute (empty, private by default). It also differentiates from sibling tools like scaleway_s3_get_bucket_tagging or scaleway_s3_set_bucket_versioning by explicitly mentioning configuration tools and their naming pattern.

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 tells when not to configure settings at creation: 'Configure it afterwards with the scaleway_s3_*_bucket_* config tools.' It also warns that 'Object Lock cannot be enabled at creation on Scaleway' and provides the correct workflow: 'enable versioning then scaleway_s3_enable_object_lock afterwards.' This gives clear when-to-use and when-not-to-use guidance.

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