ncloud_nks_delete_worker_node

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description adds a warning emoji and the requirement for confirm=true, which is also in the schema. It does not contradict annotations, but adds minimal behavioral context beyond what annotations and schema provide.

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 extremely concise—one sentence with a warning emoji. It efficiently communicates the destructive nature and the confirmation requirement without any superfluous 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 destructive action, the description is minimal. It does not explain consequences like node termination or removal from the cluster, nor does it mention prerequisites. However, combined with annotations and schema, it covers the basic required information.

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 each parameter is already documented. The description adds 'Set confirm=true to execute' which repeats the schema's parameter description. No additional semantics are provided for other parameters.

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 tool deletes a specific worker node from an NKS cluster. It uses a warning emoji and the word 'Destructive' to convey the action, and the name distinguishes it from sibling tools like ncloud_nks_delete_cluster and ncloud_nks_delete_node_pool.

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 mentions that confirm must be set to true to execute, which is a key safety requirement, but does not provide guidance on when to use this tool vs alternatives like deleting a node pool or cluster. No exclusions or explicit context for selection are given.

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