ncloud_export_cache_backup

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

Annotations declare readOnlyHint=true, and the description does not contradict this; 'export' implies copying data with no mutation of the source. The description adds the destination context ('to Object Storage'), but it does not disclose aspects like whether existing objects are overwritten, whether the operation is asynchronous, or any access requirements. It adds minimal behavioral context beyond the 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, short sentence that front-loads the action verb and resource. Every word is informative, and there is no redundant or extraneous 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?

The tool has no output schema, so the description should compensate by explaining the operation's outcome, but it only states the high-level function. The schema fully documents parameters, covering the inputs, but the description omits workflow details (e.g., why cloudCacheExportObjectList is a list, how it relates to a backup file, or post-export behavior). It is adequate but leaves gaps for a new agent.

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%, with all five parameters having descriptions. The tool description does not add parameter-specific detail beyond what the schema already provides, so the baseline of 3 applies. The description's mention of Object Storage aligns with the bucketName/folderPath parameters but adds no extra semantics.

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 uses a specific verb ('Export') and names the exact resource ('Cloud Cache backup file') and destination ('Object Storage'), clearly distinguishing it from sibling tools like list or create backup operations. It is unambiguous and directly states the tool's function.

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 no guidance on when to use this tool versus alternatives such as ncloud_create_cache_manual_backup or other export backup tools (e.g., ncloud_export_mysql_backup). It does not mention prerequisites, ordering, or scenarios where this tool is preferred, leaving the agent without usage context.

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