ncloud_delete_load_balancers

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

The description adds the critical detail that the operation requires confirm=true to execute, which is beyond the destructiveHint annotation. It also emphasizes permanence, providing useful context for the agent.

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 concise sentence with a clear warning and a direct instruction for usage. Every word is necessary, and it is front-loaded with the destructive nature.

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 covers the essential behavior (destructive, confirm requirement) for a simple delete operation. However, it omits details about the return value or behavior for non-existent instances, which would enhance completeness given no output schema.

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?

With 100% schema coverage, the schema already documents both parameters. The description repeats the confirm instruction but adds no new semantic insights beyond what the schema provides, resulting in baseline score.

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 verb 'delete' and resource 'load balancer instances', fulfilling a specific purpose. However, it does not distinguish from sibling tools like ncloud_create_load_balancer or ncloud_list_load_balancers, missing explicit differentiation.

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?

No guidance is provided on when to use this tool versus alternative tools (e.g., for temporary removal vs. permanent deletion). The only usage instruction is the confirm parameter requirement, which is more behavioral than comparative.

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