ncloud_cdss_get_subnet_list

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

The description aligns with the readOnlyHint=true annotation, indicating a safe read operation. However, it adds no extra behavioral context beyond what annotations provide (e.g., pagination, response structure, or potential limitations).

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 that conveys the essential action and context. It is front-loaded and contains no extraneous 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 simple list tool with one optional parameter and a read-only annotation, the description is adequate. The lack of an output schema is mitigated by the straightforward nature of the operation, though mentioning return fields could enhance completeness.

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 has 100% coverage for the one parameter vpcNo, with a clear description in the schema itself. The tool description does not add additional meaning or clarification beyond the schema baseline.

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 action ('Get available subnet list') and context ('for CDSS cluster creation'), distinguishing it from general subnet listing tools like ncloud_list_subnets and sibling CDSS tools like ncloud_cdss_get_vpc_list.

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 during CDSS cluster creation but does not explicitly state when to use this tool versus alternatives (e.g., ncloud_list_subnets for general subnet queries). No exclusions or prerequisites are mentioned.

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