ncloud_delete_mysql_users

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

Annotations already mark the tool as destructive and idempotent. The description adds the confirm flag requirement, which is useful. However, it does not clarify what happens when confirm=false (e.g., dry-run or preview), nor does it mention any prerequisites, rate limits, or authorization needs. With annotations covering the basic behavior, the description adds moderate value.

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 one sentence with a clear warning. It uses a visual indicator (⚠️) and front-loads the critical information. Every word serves a purpose with no redundancy.

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?

Given the lack of an output schema, the description should explain return values or confirm what happens after deletion. It does not. Additionally, there is no mention of prerequisites (e.g., instance must exist) or post-conditions. For a destructive tool, this is a significant gap, leaving the agent without full understanding of the tool's behavior.

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 fully describes all three parameters with 100% coverage. The description's mention of 'Set confirm=true to execute' adds context to the confirm parameter beyond the schema, but for the other parameters, no additional meaning is provided. Baseline 3 is appropriate.

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?

Clearly states the action (delete users) and the target resource (MySQL instance). The description includes a warning emoji and clarifies the confirm flag, making the purpose unmistakable. It effectively distinguishes from sibling tools like ncloud_add_mysql_users or ncloud_change_mysql_users.

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 only usage guideline is 'Set confirm=true to execute,' which addresses the safeguard but does not explain when to use this tool versus alternatives like changing users or deleting databases. No explicit when-to-use or when-not-to-use context is provided.

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