ncloud_get_mongodb_target_vpcs

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

The readOnlyHint annotation already declares the operation as safe and read-only. The description 'List' is consistent and adds that the scope is MongoDB VPCs, but provides no additional behavioral details like pagination or response contents. With annotations covering the safety profile, this is adequate.

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 that is clear, direct, and free of redundant information. It is highly efficient for an agent to parse and understand.

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 list tool with one optional parameter and full schema coverage, the description is nearly complete. It lacks an explicit statement about the response format or that it returns VPC IDs, but the name and verb make this inferable. Minor gap, so a 4 is appropriate.

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 fully describes the single optional parameter regionCode with a clear description of allowed values (KR, KRS). Since schema coverage is 100%, the description does not need to add parameter details, and the baseline of 3 applies.

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 the specific verb 'List' and clearly names the resource 'VPCs available for Cloud DB for MongoDB', making the tool's purpose unambiguous. It distinguishes itself from sibling tools like ncloud_get_mysql_target_vpcs and ncloud_get_cache_target_vpcs by specifying the MongoDB service.

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 the tool is used when listing VPCs for MongoDB, but it does not explicitly state when to use it over alternatives or provide any prerequisites or exclusions. The resource-specific wording gives some context, but there's no explicit guidance on when not to use it.

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