ncloud_delete_vpc_peering

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

While annotations already include destructiveHint=true, the description adds value by explicitly stating 'Permanently delete' and by disclosing the confirm=true safety guard, which is a behavioral trait not fully captured by the annotation. The idempotentHint=true annotation is not contradicted, and the description adds context about irreversibility.

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, front-loaded sentence that includes a warning symbol, the destructive action, and the key confirmation requirement. Every word earns its place, with no unnecessary filler.

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 delete operation with clear annotations and schema, the description covers the critical aspects: the destructive, permanent nature and the safety switch. It does not explain what happens after deletion or any dependencies, but those are not essential for a tool with this simplicity and annotation coverage.

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 covers 100% of parameters with clear descriptions, including the confirm flag's purpose. The description's 'Set confirm=true to execute' restates the schema's confirm description but does not add new details about parameter formats or relationships. Baseline 3 is appropriate given the high schema coverage.

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 states the action ('delete') and the resource ('VPC Peering connection'), and adds the adverb 'Permanently' to convey irreversibility. It is specific enough, though it does not explicitly differentiate from sibling tools like ncloud_accept_reject_vpc_peering or ncloud_set_vpc_peering_description, which operate on the same resource.

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 for deleting a VPC peering connection and requires confirm=true to execute, giving a clear precondition. However, it does not mention when not to use it or provide alternatives, so usage guidance is minimal but not misleading.

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