ncloud_delete_mongodb_instance

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

The description warns that the operation is destructive and permanent, adding value beyond the destructiveHint annotation by specifying 'permanently delete' and the confirm requirement. It could further clarify idempotent behavior or prerequisites.

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 at two sentences, with the core purpose front-loaded. Every word adds value, and there is no unnecessary content.

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 simple delete operation, the description adequately covers the destructive nature, permanence, and usage requirement. It lacks details like response behavior or prerequisites, but these are implicitly covered by annotations and 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 coverage is 100% and already describes both parameters. The description only reiterates the confirm requirement without adding new semantics, so it meets the baseline but does not exceed it.

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 the verb (delete) and resource (Cloud DB for MongoDB instance), making the tool's purpose specific and unambiguous. It distinguishes from sibling tools by explicitly naming MongoDB.

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 a clear instruction to set confirm=true to execute, which is a critical usage guideline. However, it does not explicitly compare to alternative deletion tools or state when not to use it.

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