ncloud_delete_postgresql_read_replica

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

Annotations already declare destructiveHint=true, and the description adds the confirm parameter requirement. However, it does not disclose additional behavioral traits such as whether the deletion is reversible, impact on dependent resources, or any rate limiting. The description adds minimal value beyond what annotations provide.

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 with a single sentence, includes a warning icon for visibility, and front-loads the purpose. Every word is necessary and there is 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?

Given the tool's simplicity (destructive, 2 params, no output schema), the description covers the essential aspects: what the tool does and the safety condition. It lacks details on return status, error handling, or post-deletion state, but for a delete operation this is acceptable.

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%, and the description adds value by explaining the confirm parameter's purpose ('Must be true to actually execute'). This goes beyond the schema's default value description. The other parameter is not elaborated, but schema handles it adequately.

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 identifies the tool as deleting a 'Cloud DB for PostgreSQL Read Replica instance', specifying both the resource type (read replica) and the action (delete). This distinguishes it from sibling tools like ncloud_delete_postgresql_instance or ncloud_delete_postgresql_databases.

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 explicitly requires 'Set confirm=true to execute', which is a crucial safety guideline. However, it does not specify when to use this tool versus alternatives (e.g., deleting the primary instance instead of the replica) or warn against misuse.

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