ncloud_serverless_delete_user

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

Goes beyond annotations by specifying the HTTP method (DELETE), the async 202 Operation response, and the admin-user 400 restriction. The warning and confirm requirement reinforce destructiveHint. No contradiction with idempotentHint.

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 dense sentences, front-loaded with the destructive warning, then endpoint, constraint, and execution requirement. No filler.

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 delete with 3 params and no output schema, it covers the endpoint, async operation, required confirmation, and a key error condition. Could add a note on polling the returned operation, but the sibling get_operation_status exists and the 202 mention is sufficient.

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 already describes clusterName and confirm with descriptions; description adds the admin-user restriction on userName and reinforces confirm, but adds no per-parameter detail beyond that. Baseline 3 with a small increment from the admin constraint.

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?

States a specific verb and resource: 'Delete a DB user' with the exact HTTP DELETE endpoint and path parameters. Clearly distinguishes from sibling serverless user tools (list/get/create/update/batch_delete) by naming the resource and API scope.

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?

Gives clear context: this is a destructive single-user deletion requiring confirm=true, and the reserved admin user cannot be deleted. However, it does not explicitly mention when to prefer this over the sibling batch_delete_users, leaving exclusion guidance to inference.

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