ncloud_flush_cache_server

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

Annotations already include destructiveHint=true, so the baseline safety signal is present. The description adds valuable detail beyond that: 'Permanently deletes ALL data' emphasizes irreversibility, and the confirm=true guard explains the required safety mechanism. This enriches the agent's understanding of the operation's side effects without contradicting 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, front-loaded sentence. It begins with a warning symbol and the word 'Destructive', immediately conveying the critical safety concern. Every phrase ('Permanently deletes ALL data', 'FlushAll', 'Set confirm=true') adds necessary information with zero wasted 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 a guard, the description covers the essential behavior: what it does (deletes all data), the severity (permanent), and the execution requirement (confirm=true). With no output schema, not describing return values is acceptable. The tool is simple enough that this description is adequately complete, though could mention response or failure modes.

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 description coverage is 100%: both parameters have clear descriptions (confirm: 'Must be true to actually execute the destructive operation'; cloudCacheServerInstanceNo: 'Cloud Cache server instance number to flush'). The tool description essentially restates the confirm requirement, adding no new semantic information. Baseline of 3 is appropriate given the schema does the heavy lifting.

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 'Permanently deletes ALL data from a Cloud Cache server (FlushAll)' uses a specific verb (deletes), names the resource (Cloud Cache server), and clarifies scope (ALL data, FlushAll). This clearly distinguishes it from other cache-related tools in the sibling list, which generally perform create/read/update operations.

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 clear usage context by warning 'Destructive' and stating 'Set confirm=true to execute.' This tells the agent when to use the tool (and when to be cautious), but it does not explicitly name alternatives or exclusions. Still, the context is strong enough to guide proper invocation.

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