ncloud_nks_delete_cluster

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

Annotations already indicate destructiveHint and idempotentHint. The description adds that the deletion is permanent and requires confirm=true for execution. This is consistent with annotations, though it could disclose more about the effect on associated resources.

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 concise sentence with a warning emoji, front-loaded with critical information. Every word serves a purpose without 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 delete operation with good annotations and full schema coverage, the description adequately conveys the destructive nature and required parameter. However, it does not mention return values or prerequisites, but these are less critical for a delete tool.

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?

The input schema already describes both parameters (clusterUuid and confirm) with 100% coverage. The description restates the need to set confirm=true, adding marginal value beyond the schema.

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 action 'delete' and the resource 'NKS Kubernetes cluster'. It is specific and distinguishes from sibling tools like ncloud_nks_create_cluster or ncloud_nks_list_clusters.

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 instructs to set confirm=true to execute, providing clear usage guidance. It implies caution with the warning emoji and 'Destructive' label, but does not explicitly state when to use this tool versus alternatives, though the context of deletion is self-evident.

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