ncloud_delete_network_interface

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description adds the specific safety mechanism (confirm flag) and the word 'permanently', which reinforces irreversibility. However, it does not disclose other behaviors like failure conditions (e.g., if interface is attached) or if deletion is immediate.

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 very concise: a single sentence with a warning emoji, front-loaded with the key idea. No redundant 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?

The tool has no output schema and the description does not mention return values, error conditions, or idempotency (though annotations cover that). It lacks context on prerequisites or postconditions, making it partially complete for a simple delete operation.

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% with both parameters fully described. The description reiterates the confirm parameter's role but does not add new meaning beyond the schema. Therefore, the description adds minimal value.

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 'Permanently delete a network interface', specifying both the action (delete) and resource (network interface). This distinguishes it from sibling tools like list, get, create, and attach/detach.

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 only mentions 'Set confirm=true to execute' but does not provide guidance on when to use this tool versus alternatives, prerequisites (e.g., interface must be detached), or consequences of deletion.

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