ncloud_list_cache_instances

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

Annotations declare readOnlyHint=true, and the description confirms a read-only list operation. However, the description does not add any behavioral context beyond what annotations already provide, such as pagination behavior or response structure.

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 sentence of 15 words, directly stating the purpose without any fluff. Every word earns its place, and it is front-loaded with the essential information.

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 list operation with readOnlyHint=true and no output schema, the description is largely sufficient. It could benefit from mentioning return value structure, but as a list tool the purpose is clear. Slightly docked for lack of output detail.

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 all 4 parameters (pageNo, pageSize, cloudCacheServiceName, cloudCacheInstanceNoList). The tool description adds no additional meaning beyond the schema, so baseline score of 3 applies.

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 'List all Cloud DB for Cache (Redis/Valkey) instances' with a specific verb and resource, and includes the scope 'in the current region'. It distinguishes this tool from sibling tools like ncloud_get_cache_instance_detail and ncloud_list_cache_backups.

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 implies use for listing cache instances, but provides no explicit guidance on when to use this tool vs alternatives (e.g., ncloud_get_cache_instance_detail for a single instance). No 'when-not-to-use' or alternative suggestions are given.

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