ncloud_serverless_batch_delete_databases

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

Annotations already signal destructiveHint=true and idempotentHint=true, and the description adds valuable context: all data is dropped, the operation is atomic, the request is accepted asynchronously (202 Operation), and execution requires confirm=true. This goes beyond the annotations without contradicting 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?

A single dense sentence front-loads the warning, then states scope, atomicity, the endpoint, the async response, and the confirmation requirement with no wasted words. Every element contributes to correct and safe invocation.

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 three-parameter destructive tool with no output schema, the description covers the essential operational facts: what is dropped, how many, the atomic guarantee, the async 202 response, and the confirmation gate. It could mention what to poll for completion or explicitly route single deletes elsewhere, but the provided context is sufficient for safe use.

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 description coverage is 100%, so the baseline is 3. The description adds the confirm=true execution gate in prose, but names, clusterName, and confirm are already well documented in the input schema. The description does not significantly extend parameter meaning beyond the schema.

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 ('Drop'), a specific resource ('1-10 databases'), and a critical consequence ('and all their data'), with an explicit HTTP endpoint. This distinguishes it from single-database delete siblings via the batch scope and count range.

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 frames when this tool is appropriate: dropping 1-10 databases in one operation atomically. It does not name sibling alternatives or explicitly state when not to use it, but the scope and destructive warning make the intended usage context clear.

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