ncloud_get_mssql_target_vpcs

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

The readOnlyHint annotation already indicates this is a safe read operation. The description adds value by specifying that the VPCs are 'available for Cloud DB for MSSQL,' which clarifies the purpose beyond just listing VPCs. No additional behavioral traits are needed for this simple list operation.

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 that immediately conveys the action and resource. No extraneous information is included, making it highly efficient for an AI agent to parse.

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 optional parameter and no output schema, the description is sufficient. It clearly states what the tool does and the relevant context (MSSQL). While it does not mention authentication or error cases, these are typically covered by the overall API context.

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?

The schema description coverage is 100% (the only parameter 'regionCode' is fully described in the schema). The tool description does not add any additional meaning to the parameter; the schema already provides clear instructions on usage and default behavior.

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 'List VPCs available for Cloud DB for MSSQL' clearly specifies the verb (list), resource (VPCs), and context (available for MSSQL). It effectively distinguishes this tool from generic VPC listing tools like ncloud_list_vpcs and from sibling tools for other database services (e.g., ncloud_get_mysql_target_vpcs).

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 VPCs that can be used with Cloud DB for MSSQL, but it does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites. The context is implied by the tool name and description.

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