ncloud_ses_get_subnet_list

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

The description is consistent with the readOnlyHint annotation, but adds no additional behavioral context beyond the annotation. It does not mention pagination, auth, or return format, though the tool is a simple read-only list operation.

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 communicates the tool's purpose and scope with no unnecessary words or fluff.

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 read-only tool with one parameter, the description is largely complete. It clearly states what it returns (subnet list) and its purpose (cluster creation). However, the lack of differentiation from the g3 variant and absence of any output schema details mean it is not fully complete.

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 description for vpcNo ('VPC number'). The tool description adds no extra parameter context, but the schema already fully documents the single required parameter.

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 'Get' and the resource 'available subnet list', with a specific context of 'for Search Engine Service cluster creation'. It distinguishes from other services' subnet list tools, but does not differentiate from the sibling tool ncloud_ses_get_subnet_list_g3.

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 phrase 'for Search Engine Service cluster creation' implies when to use (as a prerequisite for cluster creation), but there is no explicit guidance on alternatives or exclusions. Given the presence of a similar sibling tool (get_subnet_list_g3), the description misses the opportunity to clarify which variant to choose.

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