ncloud_delete_mongodb_instance

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description adds behavioral context beyond those flags: the deletion is permanent and requires confirm=true to execute. This enhances understanding of the tool's impact without contradicting the annotations.

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, front-loaded sentence with a warning icon, stating the destructive action and the confirmation requirement. Every word earns its place, and there is no redundant 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 simple delete operation with only two parameters and annotations covering destructive/idempotent behavior, the description covers the essential context: permanent deletion and the need for confirm=true. It does not explain return values or async behavior, but this is not a significant gap given the tool's simplicity.

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% with meaningful descriptions for both parameters. The description merely reiterates the confirm parameter's role ('Set confirm=true to execute') without adding new information or clarifying nuances beyond what the schema already provides.

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 ('Permanently delete') and the specific resource ('Cloud DB for MongoDB instance'), which distinguishes it from sibling deletion tools for other resources. The warning and confirmation requirement further clarify the tool's destructive 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?

The description implies use when a MongoDB instance needs to be deleted and provides the key execution guideline ('Set confirm=true to execute'). It does not mention explicit exclusions or alternatives, but the resource-specific naming makes the usage context clear.

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