ncloud_delete_load_balancers

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

Annotations already include destructiveHint=true, but the description adds behavioral context by specifying 'Permanently' and requiring confirm=true. This goes beyond the annotation by clarifying the irreversible nature and the need for explicit confirmation. 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?

The description is one concise sentence with a clear warning emoji. It fronts the destructive nature and immediately tells the agent what to do (set confirm=true). No unnecessary words or repetition.

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 destructive delete operation, the description covers the critical facts: permanence, the need for confirmation, and the target resource. Minor gaps like behavior when confirm=false or post-deletion effects are not mentioned, but given the annotations and simple schema, it is sufficiently complete for an agent to invoke correctly.

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 description coverage is 100%, so both confirm and loadBalancerInstanceNoList are already documented in the schema. The description's mention of 'Set confirm=true to execute' is redundant with the schema's confirmation requirement, adding no new semantic meaning.

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 specific action: 'Permanently delete load balancer instances.' This distinguishes it from sibling tools that list, get, or create load balancers. The verb 'delete' combined with the resource makes the purpose unambiguous.

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 when to use this tool (when permanent deletion of load balancers is needed) and provides a key execution guideline ('Set confirm=true to execute'). However, it does not explicitly mention alternatives or when not to use it, such as using delete_lb_listeners for removing only listeners.

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