ncloud_serverless_batch_delete_users

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

Annotations already declare destructiveHint and idempotentHint. The description adds critical behavior: it requires confirm=true to actually execute, and notes the operation is atomic and asynchronous (202 Operation). This goes beyond the annotations by explaining the confirmation gate and atomicity, which are not conveyed by hints alone.

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, tight sentence with a warning emoji front-loaded. It packs the destructive nature, the operation scope, the endpoint, and the confirm requirement into minimal words. Slightly more than necessary (endpoint and response code) but not bloated.

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 batch delete, the description covers the key aspects: it is destructive, requires confirmation, is atomic, and is asynchronous. It does not explain what happens if confirm is false (e.g., no-op) or any rollback, but given the annotations and schema, these are minor gaps. No output schema is present, so the 202 reference gives a hint of the response.

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 covers 100% of parameters with descriptions, including the confirm requirement and the names array constraints. The description restates 'Set confirm=true to execute' but adds no new parameter semantics beyond what the schema already provides. Baseline of 3 applies given high schema coverage.

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 ('Delete'), a specific resource ('DB users'), and a clear scope (1-10, atomically). It distinguishes from the sibling ncloud_serverless_delete_user by explicitly noting the batch nature. The endpoint and response code add precision.

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 implies usage for batch deletion (the word 'batch' is in the name and it states 1-10), but it does not explicitly say when to use this over the singular delete_user or mention any alternative. No 'use when' or 'instead of' guidance is given, so the agent must infer from the name and scope.

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