ncloud_delete_cache_instance

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

Annotations already include destructiveHint: true and idempotentHint: true. The description adds value with a warning emoji, 'Destructive,' and the confirm mechanism, which provides additional safety context beyond annotations. No contradiction.

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 two sentences. It is front-loaded with the warning and clearly structures the required action and parameter condition. No extraneous words.

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 destructive operation with two parameters and no output schema, the description is complete. It explains the action, the destructive nature, and the confirm requirement. Annotations provide additional safety hints. No gaps.

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 descriptions for both parameters. The description adds value by explaining the confirm parameter's purpose: 'Must be true to actually execute the destructive operation.' This clarifies the parameter's role beyond the schema description.

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), the resource (Cloud DB for Cache instance with Redis/Valkey), and distinguishes from sibling tools like ncloud_list_cache_instances and ncloud_get_cache_instance_detail. The verb 'delete' and resource are explicit.

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 gives a clear usage condition: 'Set confirm=true to execute.' This tells the agent when to use the tool (only with confirm=true). It does not explicitly mention when not to use it or alternatives, but the simple destructive operation makes this sufficient.

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