ncloud_delete_mssql_instance

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

Although annotations already mark the tool as destructive, the description adds behavioral context: the operation is permanent and requires a confirmation flag. This goes beyond the annotations by specifying the condition for actual execution and emphasizing irreversibility.

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 extremely concise at two sentences. It front-loads the purpose and critical usage instruction without any extraneous information. Every sentence earns its place.

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 tool, the description covers key aspects: permanence, confirm requirement, and instance identification. However, it lacks context on what happens to associated resources (backups, linked services) or any error conditions, which could help the agent make safer decisions.

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?

Both parameters are fully described in the schema (100% coverage). The description adds no new parameter semantics beyond the schema; it briefly mentions the confirm parameter but does not enhance understanding of its meaning or format.

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 tool's purpose as 'Permanently delete a Cloud DB for MSSQL instance', which is a specific verb and resource. It distinguishes from sibling tools like ncloud_delete_mssql_server, which targets servers within an instance.

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 provides an important usage instruction ('Set confirm=true to execute') but does not explicitly guide when to use this tool versus other deletion tools or when not to use it. The guidance is implied through the destructive warning.

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