Deletes an IaaS zone by ID, removing that zone from VCF Automation infrastructure management.
Delete a zone DELETE /iaas/api/zones/{id}
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The ID of the zone. (path) | |
| apiVersion | No | The version of the API in yyyy-MM-dd format (UTC). For versioning information refer to /iaas/api/about |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true. The description adds only the endpoint and does not explain cascading effects, required permissions, or irreversibility beyond what the annotations provide.
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 two short lines, front-loads the action, and contains no filler. The endpoint line is terse and useful for API mapping.
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 destructive single-resource delete, the schema and annotations cover the required ID and safety hints. However, the description omits dependency or cascade warnings and return behavior, and no output schema exists to fill that gap.
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 id documented as the zone ID path parameter and apiVersion also described. The description adds the endpoint path but no additional meaning beyond the schema.
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?
States a specific verb and resource ('Delete a zone') plus the REST endpoint, so the action is immediately clear. It does not explicitly distinguish itself from siblings like iaas_get_zone or iaas_update_zone, but the name and description are specific enough.
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?
There is no guidance on when to use this tool versus alternatives, no prerequisites, and no warning about when not to delete a zone. The agent must infer usage from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.