vpc_delete_instance

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

The description only states 'delete', which implies destruction, but with no annotations provided, there is no disclosure of critical behavioral traits such as irreversibility, required instance state, impact on associated resources, or any rate limits. This is a significant gap.

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 short ('Delete a VSI'), which is concise but insufficiently informative. While it is front-loaded, it sacrifices necessary detail for brevity. It earns a middle score for being concise but not appropriately sized.

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 complexity (2 params, no annotations, no output schema), the description fails to provide enough context. It does not explain the optional region parameter or any result of the deletion, leaving the agent underinformed for correct invocation.

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 coverage is 0% with no parameter descriptions. The description does not mention the parameters (instance_id, region) or their roles, failing to add meaning beyond the bare schema. The agent has no clue which parameter is required or how to use region.

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 'Delete a VSI' clearly states the action (delete) and the resource (VSI - virtual server instance). It effectively distinguishes itself from sibling tools like vpc_create_instance or vpc_list_instances by specifying the deletion operation.

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 like vpc_stop_instance or vpc_reboot_instance. There is no mention of prerequisites (e.g., instance must be stopped) or side effects, leaving the agent without context for appropriate usage.

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