ncloud_delete_cache_instance

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

The description adds meaningful behavioral context beyond the destructiveHint annotation by specifying 'permanently delete' and explicitly requiring 'Set confirm=true to execute.' This informs the agent of both the irreversibility and the needed confirmation, which is valuable for a destructive action. It does not contradict any annotations.

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, tightly crafted sentence that front-loads the destructive warning and clearly states the action and requirement. Every word earns its place: warning, permanence, resource type, and the execution prerequisite. No wasted text.

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 (2 parameters, no output schema) and the strong annotations, the description sufficiently covers the core context: what is deleted, that it's permanent, and that confirmation is required. It does not document secondary effects or prerequisites, but for a straightforward delete operation, the provided information is complete enough for an agent to act correctly.

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% with both parameters described, so the baseline is 3. The description adds value by explicitly stating 'Set confirm=true to execute,' which reinforces the confirm parameter's critical role in enabling the destructive operation. This explanation improves the agent's understanding of how to correctly invoke the tool.

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 action: 'Permanently delete a Cloud DB for Cache (Redis/Valkey) instance.' The verb 'delete' is specific, the resource type is explicit, and the 'permanently' qualifier distinguishes it from other cache-related operations. It clearly differentiates from sibling tools by narrowing scope to Cache instances.

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 conveys when to use this tool—when you want to permanently delete a Cache instance—but it does not explicitly mention alternatives or when-not-to-use scenarios. While the context is clear, it lacks explicit exclusionary guidance or references to alternative tools for similar operations.

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