ncloud_terminate_server

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

Annotations already provide destructiveHint=true and idempotentHint=true. The description adds valuable context: it pre-checks server status and protection, returns instructions instead of failing, and requires confirm=true to execute. 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 pack critical information: action, prerequisites, pre-check behavior, and execution requirement. No filler, front-loaded with warning.

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?

Given no output schema, the description covers the key behavioral aspects: destructiveness, prerequisites, pre-check logic, and confirm parameter. It omits return format and error cases, but the pre-check detail compensates for the complexity of the 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 described. The description adds that 'confirm' must be true to execute, and hints at the array parameter's role (terminating multiple servers). This goes beyond the schema by explaining the execution flow.

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 action (terminate/delete server instances) and the resource (server instances), with a warning icon emphasizing destructiveness. It distinguishes from siblings like ncloud_stop_server by specifying permanent deletion and prerequisites (stopped and not protected).

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 explains when to use (to permanently delete servers) and includes prerequisites (server must be stopped and not termination-protected). It also mentions alternative behavior when conditions aren't met (pre-checks and returns what to do). However, it could be more explicit about when NOT to use (e.g., for temporary shutdown, use stop).

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