ncloud_get_cache_products

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

The description matches the readOnlyHint annotation (a read operation), but adds no additional behavioral context such as pagination, return format, or required permissions. With annotations already declaring the read-only aspect, the description provides minimal extra value.

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, focused sentence with no redundant or filler content. It is appropriately concise for a simple 1-parameter read tool.

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 one-parameter read tool with a readOnlyHint annotation, the description is largely sufficient. It states the purpose and the output (product codes), and the schema covers the input. However, the lack of an explicit note about the output structure or possible empty results is a minor gap.

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 schema already fully describes the single parameter with 100% coverage. The description only restates the same concept ('for a given image') without adding formats, constraints, or how to obtain a valid product code.

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 server spec product codes', and the constraint 'for a given image'. This distinguishes it from sibling tools like ncloud_get_cache_image_products, which lists image products rather than spec product codes.

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 usage context is implied: call this when you need spec product codes for a specific Cloud Cache image. However, it does not explicitly mention when not to use it or suggest alternative tools, leaving some ambiguity given the many similar product-listing siblings.

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