ncloud_get_cache_image_products

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

Annotations already declare readOnlyHint=true, so no conflict. The description adds that it lists 'available' versions but does not clarify behavior when regionCode is omitted (e.g., all regions or default). Response format and pagination are not mentioned, but the tool is simple and read-only.

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?

A single, front-loaded sentence of 9 words. The verb and object are immediately clear. No wasted words or redundancy.

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 listing tool with one optional parameter and annotations, the description is nearly complete. It could mention that the codes are used when creating a cache instance (ncloud_create_cache_instance), but the current description suffices.

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 a clear parameter description. The tool description does not add meaning beyond the schema (e.g., effect of omitting regionCode). Baseline 3 is appropriate.

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 verb 'List', the resource 'Cloud Cache image product codes', and clarifies what those are (Redis/Valkey versions). It effectively distinguishes from siblings like ncloud_get_cache_products and other get_image_products 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?

The description implies usage (listing image codes before creating a cache instance) but does not explicitly state when to use this tool versus alternatives like ncloud_get_cache_products. No guidance on when not to use it or how it differs from similar tools.

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