ncloud_detach_network_interface

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

Annotations already indicate idempotentHint=true and destructiveHint=false, covering the operation's safety profile. The description adds the 'from a server instance' scoping but does not disclose additional behavioral traits such as whether the server must be stopped, whether the operation is reversible, or any post-condition effects.

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 of eight words: 'Detach a network interface from a server instance.' Every word earns its place with no redundancy or filler.

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 two-parameter tool with full schema coverage, annotations, and no output schema, the description is complete enough to understand the operation. It clearly identifies the action and objects involved, though it does not mention any prerequisites or return behavior, which are not necessary for this level of 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% with both parameters (networkInterfaceNo and serverInstanceNo) having descriptions. The tool description adds the relationship 'from a server instance' but does not provide additional parameter-level meaning beyond what the schema already states, so the baseline of 3 is appropriate.

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 the specific verb 'Detach' with a clear resource ('network interface') and target ('server instance'), unambiguously distinguishing it from siblings like ncloud_attach_network_interface, ncloud_create_network_interface, and ncloud_delete_network_interface.

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 implies usage (use when you need to detach a network interface from a server) but does not explicitly state when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites. The sibling list provides context, but the description itself lacks explicit guidance.

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