ncloud_get_mssql_target_subnets

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

Annotations already declare readOnlyHint=true, reducing the burden on the description. The description states it lists subnets, which is consistent and adds no additional behavioral context (e.g., error states, pagination). It suffices but does not exceed what annotations imply.

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 of 12 words, front-loaded with the verb and resource. It is efficient and avoids fluff, though it could be slightly more structured by explicitly stating the required parameter.

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 listing tool with complete schema coverage and annotations, the description provides sufficient context. It covers the purpose and key elements, although it could mention the region parameter (covered in schema) and any limitations.

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%, so the baseline is 3. The description does not add meaning beyond the schema; it mentions 'within a specific instance' which maps to cloudMssqlInstanceNo, but no extra parameter details are provided.

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 specifies the verb 'List', the resource 'subnets', and the context 'Cloud DB for MSSQL within a specific instance'. It effectively distinguishes from sibling tools like ncloud_get_mysql_target_subnets or ncloud_get_mssql_target_vpcs by focusing on MSSQL subnets.

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 usage for listing subnets for an MSSQL instance but does not provide explicit guidance on when to use this tool versus alternatives like ncloud_get_mssql_target_vpcs, ncloud_list_subnets, or similar tools for other databases. There are no usage notes or prerequisites.

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