Get Scaleway bucket visibility (public/private)

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the description carries a lighter load. The description adds valuable behavior context by explaining how visibility is derived from ACL grants and that it returns raw grants, which is beyond the annotations. No contradictions.

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 two sentences: the first explains what the tool does and how, the second notes an additional return detail. Zero waste, perfectly front-loaded and concise.

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 is a simple read operation with strong annotations (readOnlyHint, idempotentHint), two well-understood params, no output schema required, and the description covers the derivation and returns, the information provided is fully sufficient for agent selection and invocation.

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 both parameters are documented in the schema. The description does not repeat parameter syntax but provides context about the bucket and region parameters indirectly. This adds moderate value beyond the schema, so a 4 is appropriate.

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 specific verb 'Read a bucket's visibility', names the resource ('bucket visibility'), and clarifies how visibility is derived from ACL grants. This clearly distinguishes it from siblings like scaleway_s3_get_bucket_policy or scaleway_s3_get_bucket_lifecycle.

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?

Description implicitly states this tool is for reading bucket visibility, not setting it (which would be scaleway_s3_set_bucket_visibility). It explains the ACL-based derivation and provides return details ('Returns the raw grants too'). No explicit when-not-to-use guide, but the context of siblings and the read-only nature make it clear.

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