ncloud_ses_get_subnet_list

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

The readOnlyHint annotation already signals a safe read operation, and the description's 'Get' wording is consistent with that. The description adds the G2 cluster-creation context but discloses no additional behavioral details such as response contents or whether results are filtered by VPC/product code. No contradiction with annotations.

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, well-structured sentence with no filler. The key information — what is retrieved and for which workflow — is front-loaded and appropriately sized for a simple read-only list operation.

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 low-complexity read-only list tool with fully documented parameters, the description gives adequate orientation: it returns a subnet list for SES G2 cluster creation. It falls slightly short of fully complete because it does not explicitly name the G3 sibling alternative or describe the return shape, but those are minor given the simplicity and schema coverage.

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 description coverage is 100%, and both parameters already include useful source references in the schema ('from ncloud_ses_get_vpc_list' and 'from ncloud_ses_get_os_products'). The tool description itself adds no parameter-level meaning, so the schema carries the burden.

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 states a specific verb ('Get'), a resource ('available subnet list'), and the workflow context ('Search Engine Service cluster creation (G2)'). The 'G2' marker helps distinguish it from the sibling ncloud_ses_get_subnet_list_g3, though it does not explicitly name that sibling or explain what G2 means.

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 this is used when preparing SES G2 cluster creation, which suggests it should be chosen over the G3 variant. However, it does not explicitly state when to use this tool versus ncloud_ses_get_subnet_list_g3 or provide any exclusions or prerequisite guidance.

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