ncloud_get_mssql_target_vpcs

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

The readOnlyHint annotation already declares this is a safe read operation, and the description does not add additional behavioral context such as response format, pagination, or default region behavior (the latter is already in the schema). No contradiction exists; the description is consistent with annotations.

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, clear sentence that directly states the tool's purpose with no unnecessary words 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 listing tool with one optional parameter and no output schema, the description sufficiently conveys the purpose. The 'List' verb implies a return value, although it does not specify the exact structure of the VPC object returned. This is acceptable given the tool's simplicity.

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 input schema covers 100% of the single parameter (regionCode) with a description including default behavior. The tool description adds no parameter-specific information beyond what is already in the schema, so the baseline 3 is appropriate.

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 resource ('VPCs') with a clear service qualifier ('for Cloud DB for MSSQL'), making it easy to distinguish from sibling target VPC tools for other database services (e.g., MySQL, PostgreSQL, MongoDB).

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 use when the agent needs VPCs available for a MSSQL database, but it does not explicitly mention alternatives or provide when-to-use vs. when-not-to-use guidance. For a simple list tool this is adequate, but explicit sibling differentiation would improve clarity.

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