ncloud_cdss_get_os_products

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

The readOnlyHint annotation already declares this as a safe read operation. The description adds no behavioral context beyond repeating 'Get', such as return format, pagination, or regional variations. While not contradictory, it enriches the annotation only minimally, warranting a baseline score.

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, front-loaded sentence with clear verb and resource, containing no filler or redundant text. It efficiently conveys the tool's function in minimal words.

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 zero-parameter, read-only enumeration tool, the description fully captures the tool's role in the CDSS cluster creation flow. It does not need to explain return values in detail since 'available operating system types' implies a list, and the absence of an output schema does not create notable gaps at this complexity level.

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 tool has zero parameters, so the description has no parameter details to provide. Per the rubric, 0 params yields a baseline of 4; the description correctly focuses on the tool's purpose rather than irrelevant parameter guidance.

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 'Get', identifies the resource as 'operating system types', and scopes it to 'CDSS cluster creation'. This clearly distinguishes it from sibling tools like ncloud_cdss_get_cluster_server_images or ncloud_cdss_get_node_products, which target different aspects of cluster creation.

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 context of use ('for CDSS cluster creation'), helping the agent know when to call it. It does not explicitly mention alternatives or exclusions, but given the simple read-only nature, the context signal is sufficient for selection among siblings.

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