ncloud_delete_postgresql_users

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

Annotations already flag destructiveHint=true, but the description adds a critical behavioral detail: 'Set confirm=true to execute.' This clarifies that the operation is a no-op without confirmation, which is not evident from annotations. It provides a warning and prerequisite for invocation, enhancing transparency.

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 with a warning prefix and action. Every word earns its place; front-loaded with 'Destructive' and directly actionable.

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 delete operation with a well-described schema and annotations, the description is adequate. It states the action, resource, and confirmation requirement. It lacks mention of edge cases like idempotency or consequences of deleting nonexistent users, but given the concise nature and schema richness, it's sufficiently complete.

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 covers all 3 parameters with descriptions (coverage 100%), including the confirm flag's requirement. The description restates the confirm behavior but adds no new parameter-level meaning beyond the schema. It reinforces the confirmation requirement, but that's already documented. Baseline of 3 applies due to high schema coverage.

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 users from a Cloud DB for PostgreSQL instance' with a specific verb and resource. It distinguishes from sibling delete tools for the same service (e.g., delete_postgresql_databases, delete_postgresql_instance) by specifying '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 description provides no explicit when-to-use guidance or alternatives. It only gives the operation and a confirmation requirement. While the tool name and context imply usage, it does not contrast with other delete operations for the same service, so an agent would need to infer context from the name.

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