Delete Scaleway bucket CORS rules

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

Annotations show readOnlyHint=false, destructiveHint=false, but description clarifies the destructive behavioral effect (removing all CORS rules, thus disabling cross-origin access). It adds the 'default-deny' consequence which annotations don't provide, giving full transparency.

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 sentence with only 13 words, zero fluff. It front-loads the action and consequence efficiently.

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 tool (2 params, high schema coverage, no output schema), the description is complete. It explains what happens, the behavioral outcome, and when to use it, with no gaps.

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 'bucket' and 'region' parameters are documented in the schema. The description does not add extra meaning beyond what the schema already says, but that is acceptable given high schema coverage, hence baseline 3.

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 'Remove' and resource 'ALL CORS rules from a bucket'. It clearly distinguishes this tool from related sibling tools like scaleway_s3_get_bucket_cors and scaleway_s3_put_bucket_cors.

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 that after removal, browsers regain no cross-origin access (default-deny), which tells the agent exactly when to use this tool (when CORS restrictions should be removed) and implies the consequence of the action.

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