vast_delete_zone

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

The description merely restates the operation implied by the tool name ("Delete a VAST zone") and provides no additional behavioral context such as irreversibility, cascading effects on associated data, or required permissions. With no annotations provided, the description completely fails to disclose these important traits.

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 extremely brief and front-loaded, with no wasted words. However, it is under-specified for a destructive operation and misses caveats, so while concise, it is not appropriately sized for the information needed.

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?

Given the simple schema and no output schema, the description at least identifies the target entity, but it lacks essential context about the deletion's impact, the difference between deleting and archiving, and any steps required before deletion. The sibling tools show related operations, yet the description does not connect to them.

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 has 100% description coverage for the single parameter 'id' ("VAST zone ID"), so the baseline is 3. The description adds no extra meaning beyond the schema, but the schema already sufficiently documents the parameter.

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 (VAST zone), making it a specific verb+resource pairing. However, it does not differentiate from siblings like vast_delete_archived_zone or vast_archive_zone, and does not clarify scope (e.g., active vs archived zones).

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 guidance is provided on when to use this tool versus alternatives such as vast_archive_zone or vast_delete_archived_zone. There are no prerequisites, no warnings about required prior archiving, and no mention of conditions under which deletion is allowed.

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