vpc_delete

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

No annotations are provided, so the description must carry the full behavioral burden. It states only that the tool deletes a VPC and returns success confirmation. It does not disclose irreversibility, potential failure conditions (e.g., if resources are attached), or any side effects beyond deletion. The 'Smart identifier resolution' is helpful but is more about parameter handling than behavioral 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 very concise, with the action stated in the first line, followed by a brief note about identifier resolution, then an Args/Returns block. There is no irrelevant or repetitive content; every sentence earns its place. The structure is clear and 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?

Given the destructive nature of deletion and the presence of a sibling 'vpc_delete_vpc2,' the description is incomplete. It does not clarify which VPC type it targets, nor does it mention constraints like needing to detach resources first or that deletion is irreversible. The output is only described as 'Success confirmation,' which is minimal. These gaps could lead an agent to misuse the tool or fail in edge cases.

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 provides only a parameter name and type (string) with no description (schema coverage 0%). The description compensates by explaining that 'vpc_identifier' accepts either a VPC description or ID, and adds a second parameter 'ctx' for resource change notifications. This adds meaningful semantic information beyond the bare 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?

The description clearly states the verb and resource: 'Delete a VPC.' This distinguishes it conceptually from other tools, but it does not explicitly differentiate from the sibling 'vpc_delete_vpc2,' so an agent might be unsure whether this handles classic VPCs only. It is a clear, concise purpose statement but lacks explicit sibling differentiation.

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 mentions how to specify the identifier ('Use VPC description or ID') but provides no guidance on when to choose this tool over alternatives like 'vpc_delete_vpc2.' There is no mention of exclusions, prerequisites, or which VPC types are covered, so the agent gets no direct usage-direction.

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