ncloud_flush_cache_server

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

Annotations already declare destructiveHint=true. The description adds that the operation is a 'FlushAll' (deletes all data) and requires confirm=true. This adds some context beyond the annotation, but does not disclose other behavioral traits like irreversibility beyond the word 'permanently', or any impact on running services.

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, well-structured sentence with a clear warning emoji. It is concise, front-loaded with the critical destructive warning, and every word contributes value.

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 no output schema and low complexity (2 params), the description covers the essential purpose and safety requirement. It could mention return behavior or prerequisites, but it is adequate for the tool's simplicity.

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%; both parameters are described in the schema. The description only reiterates that confirm must be true, which is already in the schema. No additional meaning is added beyond the schema.

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 tool's purpose: 'Permanently deletes ALL data from a Cloud Cache server (FlushAll).' This is a specific verb+resource pair that distinguishes it from all sibling tools, none of which perform a similar flush operation.

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 critical usage guideline: 'Set confirm=true to execute.' However, it does not explicitly state when to use this tool versus alternatives, nor does it mention any prerequisites or scenarios where it should be avoided. The guideline is implicit but minimal.

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