ncloud_ses_delete_cluster

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

The description adds a clear warning that the operation is destructive and all data will be lost, which goes beyond the destructiveHint annotation. The idempotentHint annotation is not contradicted, though not explicitly addressed.

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 extremely concise, using a single line with an emoji warning and key instruction. It is front-loaded with the most critical information.

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 delete operation with two parameters, the description covers the destructive nature and confirm requirement. It lacks precondition details but is generally adequate.

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%, and the description adds meaning to the 'confirm' parameter by stating it must be true to execute. However, it does not elaborate on 'serviceGroupInstanceNo' beyond the schema description.

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 'Search Engine Service cluster', and mentions permanent deletion. It does not explicitly differentiate from sibling tools, but the context of Search Engine Service cluster is specific enough.

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 instructs to set confirm=true to execute, which is a key usage guideline. However, it does not provide when to use this tool versus alternatives, nor does it mention prerequisites like ensuring the cluster is stopped.

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