ncloud_delete_mysql_databases

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

Description reiterates destrutive hint already provided by annotations. Adds the confirm flag requirement, but no details on effects, rollback, or edge cases. Given annotations cover destrutive nature, description adds marginal 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?

Extremely concise, single sentence with front-loaded warning. No unnecessary words. Perfectly structured for quick understanding.

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 destrutive tool, description mentions the confirm flag but lacks info on return behavior, post-deletion state, or handling of non-existent databases. Adequate but not comprehensive.

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 description doesn't need to add much. The only extra info is 'Set confirm=true to execute', which is already in the schema description for confirm. No additional semantics beyond schema.

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 databases) and resource (Cloud DB for MySQL instance). The warning emoji immediately signals destrutive nature. Distinguishes from siblings by specifying MySQL.

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?

Implicitly says to set confirm=true to execute, but does not explicitly state when to use this tool vs alternatives (e.g., deleting the instance itself). Lacks guidance on when not to use it.

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