ncloud_delete_mysql_databases

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

Annotations already declare destructiveHint=true, but the description reinforces this with a warning emoji and adds critical behavioral context: 'Set confirm=true to execute.' This tells the agent that the operation is destructive and requires explicit confirmation, which is beyond what the annotations alone communicate. No contradiction exists between the description and 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, each earning its place: the first states the destructive purpose, and the second specifies the safety mechanism. It is front-loaded with a warning and is highly concise with no redundant information.

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 destructive delete operation with three parameters and no output schema, the description covers the core intent and the confirmation safeguard. It could mention potential prerequisites or side effects (e.g., data loss), but the annotations and schema fill the gap reasonably well, making the description sufficient for invocation.

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% description coverage for all three parameters. The description's mention of 'Set confirm=true to execute' aligns with the confirm parameter's schema description but adds no new meaning. With high schema coverage, the baseline is 3, and the tool description does not elevate it further.

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 'Delete databases from a Cloud DB for MySQL instance,' which uses a specific verb (delete) and resource (databases from a Cloud DB for MySQL instance). This distinguishes it from sibling tools like ncloud_delete_mysql_users and ncloud_delete_mysql_instance, which target different resources.

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 no explicit guidance on when to use this tool versus alternatives, such as ncloud_add_mysql_databases or ncloud_delete_mysql_users. It only states the action and the confirmation requirement, leaving the agent to infer usage from the name and purpose. There are no prerequisites, exclusions, or alternative tool references.

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