ncloud_delete_postgresql_instance

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description adds 'Permanently' and the confirmation requirement, offering context about irreversibility and a safety guardrail. It doesn't contradict the annotations and provides useful behavioral transparency beyond them.

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, front-loaded sentence with a warning emoji. Every word earns its place, and the critical confirmation note is included without any waste.

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 two-parameter destructive operation with annotations and no output schema, the description is sufficiently complete. It covers the operation's purpose, irreversibility, and the confirm requirement. It doesn't explain return values, but that is not necessary given the lack of an output schema.

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 description coverage is 100%, so the baseline is 3. The description reinforces that confirm must be true to execute, which adds slight meaning beyond the schema, but it doesn't provide deeper parameter semantics (e.g., format, examples, or constraints) for cloudPostgresqlInstanceNo.

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 uses a specific verb 'delete' and resource 'Cloud DB for PostgreSQL instance', clearly distinguishing it from sibling tools like ncloud_delete_postgresql_read_replica or ncloud_delete_postgresql_databases. The scope is unambiguous and immediately actionable.

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?

It clearly states the destructive nature and the requirement to set confirm=true to execute, which is key usage guidance. However, it doesn't explicitly contrast with alternative delete tools for PostgreSQL components, such as read replicas or databases, so it lacks explicit exclusions.

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