ncloud_serverless_delete_cluster

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

Beyond the destructiveHint annotation, the description discloses the destructive consequence, the confirmation guard, the cascading deletion semantics, the default behavior, and the specific 409 failure scenarios. This is far richer behavioral context than the annotation alone provides.

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 compact, front-loads the destructive warning, and packs essential operational details into three sentences with no filler. Every sentence adds meaningful 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 destructive tool with no output schema, the description covers the confirmation requirement, cascading behavior, error conditions, and async operation result (202). An agent has enough context to call the tool correctly and anticipate consequences.

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?

Although the schema already documents all three parameters with 100% coverage, the description adds crucial semantics not in the schema: cascading=false causes 409 while users/databases remain, cascading=true deletes them, and confirm must be true to execute. These details materially change how an agent should set the parameters.

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 ('Delete a Cloud DB Serverless cluster'), identifies the exact API endpoint, and names the resource type. It is unambiguous and distinct from sibling deletion tools by specifying the Cloud DB Serverless cluster context.

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 explains key operational usage details: cascading behavior, the default value, the required confirm=true to execute, and the 409 error when users/databases remain or when a restore is running. It does not explicitly name alternatives or state 'use this instead of X,' but the resource and behavior are specific enough to guide correct invocation.

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