ncloud_cdss_get_subnet_list_g3

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

Annotations declare readOnlyHint=true, so the agent knows this is a safe read operation. The description adds the scoping constraint (G3/KVM only) and the purpose (CDSS cluster creation), which is useful context. It doesn't describe return format or pagination, but for a list tool with readOnlyHint, this is acceptable.

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?

A single sentence that is concise and front-loaded with the action and resource, followed by the scoping qualifier. No wasted 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 read-only list tool with full schema coverage and readOnlyHint annotation, the description is mostly complete. It could be improved by explicitly naming the sibling tool (ncloud_cdss_get_subnet_list) to disambiguate, but the G3/KVM qualifier partially covers this.

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%, so the schema already documents all three parameters. The description adds no parameter-level detail beyond what the schema provides. Baseline 3 is appropriate when the schema carries the parameter documentation 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 a clear context ('for CDSS cluster creation (G3/KVM only)'). It distinguishes from the generic ncloud_cdss_get_subnet_list by the G3/KVM qualifier, though it doesn't explicitly name the sibling.

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 when to use it: during CDSS cluster creation, specifically for G3/KVM. It does not explicitly state when not to use it or mention alternatives like ncloud_cdss_get_subnet_list, but the G3/KVM qualifier provides some routing guidance.

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