Get Scaleway bucket CORS rules

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety and side effects. The description adds value by disclosing that the tool errors with NoSuchCORSConfiguration if no rules are set, which is a useful behavioral trait beyond the structured metadata.

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, front-loaded with the primary action ('Read a bucket's CORS rules') followed by a key behavioral note. Every word earns its place; no fluff or redundancy.

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 read tool with 2 fully-documented parameters and comprehensive annotations, the description covers the essential purpose and a notable error case. It does not describe the output format (no output schema), but given the simplicity and existing structured data, the description is sufficiently complete for an agent to call this tool correctly.

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%, with 'bucket' and 'region' already described in the schema. The tool description does not add any additional meaning or context for these parameters, so it meets the baseline but does not exceed it.

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 uses a specific verb ('Read') and resource ('a bucket's CORS rules'), clearly distinguishing this from sibling tools like scaleway_s3_put_bucket_cors or scaleway_s3_get_bucket_lifecycle. It also adds an error condition detail, making the purpose unambiguous.

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 provides no guidance on when to use this tool over alternatives such as put_bucket_cors or delete_bucket_cors. It does not mention prerequisites, context, or exclusions, leaving the agent to infer usage solely from the name and annotations.

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