ncloud_nks_delete_node_pool

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

Annotations already mark destructiveHint and idempotentHint, but the description adds valuable behavioral context: the deletion is permanent and requires confirm=true to execute. This goes beyond the structured annotations by explaining irreversibility and the safety guard, which is critical for a destructive operation.

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, front-loaded sentence with a warning symbol, clearly stating the destructive action and the confirmation requirement. Every word contributes meaning; there is no filler 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 destructive delete operation with comprehensive schema and annotations, the description adequately covers the operation's purpose, the permanence, and the confirmation gate. It does not explain return values, but no output schema exists, and the annotation set covers idempotency and destructiveness sufficiently.

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 provides 100% coverage, describing all three parameters including the confirm requirement. The description's mention of confirm=true merely restates the schema's own description ('Must be true to execute'), adding no new semantic insight beyond what structured fields already convey.

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 ('delete'), a specific resource ('node pool'), and a clear scope ('from an NKS cluster'). It clearly distinguishes this tool from similar siblings like ncloud_nks_delete_worker_node and ncloud_nks_delete_cluster by naming the exact resource being deleted.

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 clearly conveys the operation's context: permanently deleting a node pool from an NKS cluster, with a mandatory confirmation flag. It does not explicitly name alternatives or when-not-to-use scenarios, but the resource-specific wording makes the intended use unambiguous among sibling tools.

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