ncloud_create_vpc

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

Annotations include destructiveHint=false, so safety is already covered. The description adds the dryRun=true option for preview, which is a useful behavioral detail. However, it does not disclose what happens on success (e.g., return value) or any other side effects beyond what dryRun implies.

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?

Two concise sentences: the first states the primary action, the second provides a valuable dryRun tip. No unnecessary words, and the key information is front-loaded.

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 create operation with full parameter coverage and a non-destructive annotation, the description is complete enough. It could mention return values or async behavior, but these are not critical given the simplicity and high schema coverage. The dryRun tip adds useful 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?

Schema description coverage is 100%, with all three parameters clearly documented. The description only repeats the dryRun behavior already present in the schema, adding no new semantic meaning for vpcName or ipv4CidrBlock. Baseline 3 is appropriate when the schema handles parameter explanation.

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 'Create a new VPC' uses a specific verb and resource, clearly distinguishing it from sibling tools like ncloud_delete_vpc, ncloud_list_vpcs, and other ncloud_create_* tools. The purpose is unambiguous and directly tied to the tool name.

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?

No explicit when-to-use or when-not-to-use guidance is provided. The usage is implied by the name and description ('use when you need to create a VPC'), but there is no mention of alternatives or prerequisites, such as needing a VPC before subnets.

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