ncloud_delete_postgresql_databases

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description adds value by explicitly labeling as 'Destructive' and specifying the confirm parameter requirement, which is not in annotations. This provides clear behavioral context beyond the structured data.

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, consisting of a single sentence that front-loads the warning emoji and 'Destructive'. Every word earns its place, with no redundancy or filler.

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?

The description covers the essential action and the confirm safeguard. However, it lacks details on what happens after deletion (e.g., return values, confirmation, or error states) and does not address the format of the database list (though schema covers that). For a destructive tool without output schema, more context would improve completeness.

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 by noting 'Set confirm=true to execute', which clarifies the purpose of the confirm parameter beyond its schema description. No additional detail on other parameters, but the extra hint elevates the score.

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 PostgreSQL instance', using a specific verb and resource. It distinguishes from sibling tools like ncloud_add_postgresql_databases and ncloud_list_postgresql_databases by being explicitly destructive.

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 includes the key guideline 'Set confirm=true to execute', which is critical for a destructive operation. However, it does not explicitly state when to use this tool versus alternatives like ncloud_delete_postgresql_instance or ncloud_delete_postgresql_users, leaving some ambiguity for the agent.

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