ncloud_delete_bucket_cors

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description adds value by confirming the destructive nature, explaining that all cross-origin access rules will be removed, and highlighting that confirm must be true for execution. No contradiction with annotations.

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 a warning emoji and 'Destructive:', efficiently stating the action, consequence, and the confirm flag requirement. No unnecessary words.

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 destructive tool with no output schema, the description covers the purpose, the critical safety requirement (confirm=true), and the effect. It is complete enough for an agent to understand when and how to invoke it.

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 parameters. The description reinforces the confirm requirement and mentions the bucket in context, but does not add new semantic details beyond what the schema already provides. Baseline of 3 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?

The description clearly states the verb 'Delete' and the resource 'CORS configuration from a Ncloud Storage bucket', explains the consequence of removing all cross-origin access rules, and distinguishes from sibling tools like ncloud_get_bucket_cors and ncloud_put_bucket_cors. The destructive warning and confirm requirement are explicitly mentioned.

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 implicitly conveys usage (to delete CORS configuration) and explicitly states the need for confirm=true to execute. It does not explicitly mention when not to use or alternatives, but the context of sibling tools makes it clear. A more explicit guideline could be added, but it's still clear.

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