ncloud_get_cache_image_products

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

The annotations already declare readOnlyHint=true, so the agent knows this is a safe read operation. The description adds context about the content being Redis/Valkey versions but does not disclose any additional behavioral traits such as pagination, response format, or rate limits. This is acceptable for a simple list operation but adds limited value beyond the annotation.

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 concise sentence that immediately states the action and resource, with no fluff or redundancy. The parenthetical adds valuable specificity about the Redis/Valkey versions.

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 tool with one optional parameter, no output schema, and a read-only annotation, the description is sufficient. It tells the agent exactly what will be returned (image product codes) and the relevant service context. No further explanation of return values is needed since the description already indicates the output.

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 sole parameter 'regionCode' is fully documented in the schema with its description 'Region code (KR, KRS)', so schema coverage is 100%. The tool description does not add any additional meaning about how the parameter affects results, so the baseline 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 uses the specific verb 'List' and clearly identifies the resource as 'Cloud Cache image product codes' with the parenthetical '(Redis/Valkey versions)' providing necessary clarification. This distinguishes it from sibling tools like ncloud_get_cache_products or image product listings for other services.

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 clearly states the function is to list available Cloud Cache image product codes, which provides clear context for when an agent would need this tool. However, it does not explicitly mention when not to use it or contrast with alternative sibling tools like ncloud_get_cache_products, so it lacks explicit exclusions.

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