ncloud_nks_delete_node_pool

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

Annotations already provide destructiveHint=true and idempotentHint=true. The description adds context that the deletion is permanent and requires the confirm parameter to be set to true to execute. This goes beyond annotations by specifying the confirmation mechanism, though it could mention that the node pool and its nodes are irreversibly removed.

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 sentence with a warning emoji, front-loading the destructive nature. Every word is necessary and concise, with no wasted characters.

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?

The description states that the action is permanent and requires confirmation, which is sufficient for a simple delete operation. However, it does not describe the output or post-deletion state, but given no output schema, the description is reasonably complete for the tool's complexity.

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%, so baseline is 3. The description mentions the confirm parameter in the main text, but the schema already describes it as 'Must be true to execute'. No additional meaning is added beyond what the schema provides.

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 'node pool from an NKS cluster', with a warning emoji emphasizing permanence. The tool name itself is unambiguous, and sibling tools like ncloud_nks_create_node_pool and ncloud_nks_delete_worker_node make the distinction clear.

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 provides a clear precondition: 'Set confirm=true to execute'. However, it does not explicitly state when to use this tool versus alternatives (e.g., ncloud_nks_delete_worker_node) or provide any exclusion criteria. The instruction is adequate but minimal.

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