ncloud_ses_get_subnet_list_g3

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

The annotations already declare `readOnlyHint: true`, and the description ('Get') is consistent with a read-only operation. However, the description does not add any additional behavioral context beyond what the annotations provide, such as authentication requirements or limitations on the returned data.

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 of 12 words, front-loading the key action, context, and constraint. Every word is necessary and contributes to understanding. No fluff or redundancy.

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 parameter and read-only annotations, the description is fairly complete. It specifies the context (SES cluster creation) and the scope (G3/KVM). However, it does not describe the return structure or mention that the subnet list is filtered by the given VPC, which would be helpful given the absence of an output schema.

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?

With 100% schema description coverage, the baseline is 3. The description does not add any meaning beyond what the input schema provides for the single parameter `vpcNo`. It merely states the purpose, which is already clear.

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'), the context ('for Search Engine Service cluster creation'), and the constraint ('G3/KVM only'). This is a specific verb+resource combination that distinguishes it from the sibling tool `ncloud_ses_get_subnet_list`, which likely covers other generations.

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 implicitly guides usage by specifying 'G3/KVM only', indicating it should be used specifically for G3/KVM-based SES cluster creation. While it does not explicitly name alternative tools or state when not to use it, the constraint is clear enough for an agent to differentiate from general subnet listing tools.

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