ncloud_list_cache_manual_backups

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

The annotation readOnlyHint=true already declares this as a safe read operation. The description adds no further behavioral context, such as pagination behavior, default page size, or how the optional cloudCacheInstanceNo filter affects results. It does not contradict the annotation, but it contributes little beyond what the annotation already conveys.

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, clear sentence that front-loads the primary verb and resource. It is concise with no filler or wasted words, making it highly scannable for an agent.

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 simplicity of this list operation, the readOnlyHint annotation, and the fully documented optional parameters, the description is largely sufficient. It lacks an output schema or mention of return fields, but for a straightforward list tool with read-only semantics, this is acceptable. It could be improved with brief notes on pagination defaults, but it is not critically incomplete.

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?

The input schema already provides complete descriptions for all three parameters (pageNo, pageSize, cloudCacheInstanceNo) with 100% coverage. The description does not add any additional meaning or usage details beyond what the schema already specifies, matching the baseline for high schema coverage.

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 states a specific verb ('List') and resource ('manual backups for Cloud DB for Cache instances'), clearly distinguishing it from sibling tools like 'list_cache_manual_backup_details' and 'list_cache_backups'. The phrase 'manual backups' differentiates it from other backup listing tools.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or explicitly contrast with similar sibling tools, such as 'list_cache_manual_backup_details' or 'list_cache_backups'. The description only states what the tool does, not when to choose it.

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