ncloud_get_mysql_target_subnets

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

The tool is annotated as readOnlyHint=true, and the description's "List" verb aligns with this, so there is no contradiction. The description adds some context by indicating the subnets are scoped to a specific MySQL instance and intended for instance creation, but it does not disclose details such as whether only subnets in the instance's VPC are returned or how invalid instance numbers are handled.

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, front-loaded with the action and resource, and contains no unnecessary filler. The awkward "within a specific MySQL instance" wording is a minor structural flaw, but the overall length is appropriate.

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?

This is a simple two-parameter read-only tool with no output schema, and the description provides a basic but sufficient understanding of the tool's purpose. It does not clarify return value shape, whether results are paginated, or how the subnets are selected, but for a straightforward list operation the missing details are not critical.

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% for both regionCode and cloudMysqlInstanceNo, so the schema already documents the parameters. The description only weakly reinforces that cloudMysqlInstanceNo identifies the specific MySQL instance and adds no meaningful format, syntax, or value guidance beyond the schema.

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 uses a specific verb "List" and identifies the resource as "subnets available for Cloud DB for MySQL instance creation," which clearly distinguishes it from MySQL VPC listing and other database subnet tools. However, the phrase "within a specific MySQL instance" is grammatically awkward and could be misinterpreted, slightly undermining clarity.

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 intended usage is implied: the user needs to provide a specific MySQL instance and expects subnets that can be used for instance creation. There is no explicit mention of when to choose this over get_mysql_target_vpcs or other subnet-related tools, and no exclusions or alternative guidance is provided.

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