ncloud_delete_nat_gateway

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

The description supplements annotations by explicitly stating 'Permanently delete' and requiring confirm=true, providing critical safety context. While annotations already indicate destructiveness, the description adds the confirmation protocol. It does not cover all behaviors (e.g., impact on associated resources), so it is slightly incomplete.

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 and front-loaded, using a warning emoji and clear imperative language. Every word serves a purpose (destructive indicator, action, resource, execution condition).

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 deletion tool with annotations, the description covers the essential behavioral aspects: destructive nature, required confirmation, and permanence. It doesn't detail return value or conditions for failure, but given the lack of an output schema and the simplicity of the operation, the description is largely complete.

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 has 100% parameter description coverage. The tool description repeats the confirm requirement but does not add new semantic information beyond the schema. It provides no additional context for the other parameters (natGatewayInstanceNo, returnPublicIpInstance). Hence, parameter semantics are adequately covered by the schema alone.

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 'Permanently delete' and the resource 'NAT Gateway instance', distinguishing it from other NAT Gateway operations like list, get, or create.

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 minimal usage guidance: it notes the confirm flag requirement for execution. However, it does not specify when to use this tool versus alternatives (e.g., checking existence first) or the consequences of deletion beyond permanence. It is functional but not comprehensive.

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