ncloud_delete_mysql_instance

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

The description warns with the emoji and 'Destructive', and explains the confirmation guardrail. Annotations already indicate destructiveHint: true, so the description adds value by detailing the safeguard mechanism. 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 a single sentence with a warning emoji, very concise and front-loaded. Every word contributes to clarity and instruction, with no unnecessary details.

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 two-parameter destructive operation, the description is complete enough. It explains the action and the critical confirmation requirement. Lacks discussion of prerequisites (e.g., instance must exist), but that is implicit. No output schema is needed.

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 input schema has 100% coverage, so baseline is 3. The description emphasizes the confirm parameter ('Set confirm=true to execute'), which adds practical meaning beyond the schema. This extra context justifies a 4.

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 'Permanently delete a Cloud DB for MySQL instance', specifying the exact action (delete) and resource (MySQL instance). The name itself also clearly indicates this. It distinguishes from sibling tools like 'ncloud_delete_mysql_server' which suggests a different 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 explicitly instructs to 'Set confirm=true to execute', providing clear usage guidance. While it does not list alternatives or when not to use it, the instruction is sufficient for a straightforward destructive operation.

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