ncloud_ncs_delete_bucket_cors

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

Annotations already provide destructiveHint=true and idempotentHint=true, but the description adds meaningful behavior: it warns 'Destructive', states that all cross-origin access rules will be removed, and explicitly requires confirm=true to execute. This gives an agent the context needed to avoid accidental destructive actions.

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?

A single, front-loaded sentence with the service tag, destructive warning, exact resource and HTTP operation, effect, and confirmation requirement. There is no filler or redundant exposition.

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 2-parameter destructive tool with full schema coverage and destructive/idempotent annotations, the description provides adequate information: target, effect, and confirm gate. A minor gap is not stating what happens when no CORS configuration exists, though idempotentHint mitigates that concern.

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% with clear descriptions for both bucketName and confirm. The description reinforces 'Set confirm=true to execute', but this largely repeats the confirm parameter's schema description and adds no new parameter-specific semantic detail.

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 states a precise verb and resource: 'Delete the CORS configuration of a Ncloud Storage bucket', and further clarifies the effect by saying it removes all cross-origin access rules. This clearly distinguishes it from sibling tools like ncloud_ncs_get_bucket_cors, ncloud_ncs_put_bucket_cors, and delete lifecycle/encryption tools.

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?

Usage is implied: an agent needing to remove CORS configuration would select this tool. However, the description never names alternatives such as ncloud_ncs_get_bucket_cors or ncloud_ncs_put_bucket_cors, nor does it state when not to use it. 'Set confirm=true to execute' is an operational instruction rather than selection guidance.

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