ncloud_serverless_delete_database

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

Beyond the destructiveHint annotation, the description adds crucial behavior: it warns that ALL data is dropped, reveals the exact DELETE endpoint, notes the 202 Operation async response, and explains the confirm=true safety gate. This substantially exceeds what annotations alone provide and does not contradict them.

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 dense sentence that front-loads the destructive warning, then gives the endpoint, the async response, and the confirmation requirement. There is no filler or redundant content.

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 single-delete tool, the description covers the essential operational facts: what is deleted, the required confirm flag, the HTTP endpoint, and the 202 Operation response. It does not mention how to poll the resulting operation, but that is a minor omission given the clarity of the core call.

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?

The schema already describes confirm and clusterName, covering 67% of parameters. The description adds that clusterName and databaseName identify the resource in the URL path and that confirm must be true to execute, but it does not add meaning for the undocumented databaseName parameter beyond what the pattern suggests.

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 states a specific verb and resource: 'Drop a database and ALL its data', and includes the exact HTTP DELETE path. It clearly distinguishes this from sibling tools like ncloud_serverless_delete_cluster or ncloud_serverless_delete_user by naming the database resource.

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 clearly establishes that this tool is for deleting a single database and that confirm=true is required to execute. It provides clear context for when to call it, though it does not explicitly mention alternatives like ncloud_serverless_batch_delete_databases or state exclusions.

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