Delete network interface

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

The description adds detailed behavioral context beyond annotations: it explains that the tool will disconnect any VM/CT using the interface, which is not captured by the destructiveHint=true annotation alone. No contradiction with annotations.

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?

Two concise sentences delivering the core action and risk advisory. No redundant information; each sentence earns its place.

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 adequately covers the destructive nature and confirmation requirement. It could mention irreversibility or prerequisites, but the combination with schema required fields suffices for an agent to safely invoke the tool.

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 description does not directly explain the 'node' and 'iface' parameters, relying on the schema. It adds value for the 'confirm' parameter by aligning with the instruction to ask for confirmation. With schema coverage at 33%, the description partially compensates but could detail parameter roles.

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 'Delete a network interface' with a specific verb and resource, and distinguishes from siblings like create_node_network and update_node_network by highlighting the destructive nature and disconnection impact.

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 explicitly warns of high risk and instructs to ask for user confirmation. It provides clear context for when to use with caution, though it doesn't list specific alternatives or when not to use.

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