ncloud_delete_mssql_server

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

The description adds the 'Slave only' constraint and the confirm flag behavior, which goes beyond the destructiveHint annotation. There is no contradiction with 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 two sentences, front-loaded with purpose and scope, then the execution requirement. No unnecessary words.

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 annotations, the description is complete. It covers what is deleted and the mandatory confirm flag. It could mention irreversibility, but that is implied by destructiveHint.

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 coverage is 100%, so baseline is 3. The description adds value for the confirm parameter (must be true), but does not provide additional details for the cloudMssqlServerInstanceNo parameter. This is adequate.

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 tool name and description clearly indicate deletion of a Slave MSSQL server instance. It specifies 'Slave server instance from a Cloud DB for MSSQL cluster,' which differentiates it from sibling tools like ncloud_delete_mssql_instance that likely delete the entire 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 explicitly states to set confirm=true to execute, providing clear usage guidance. However, it does not mention when not to use this tool (e.g., for master server or full instance deletion) or suggest alternative tools.

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