I don't think variable names alone (and correspondingly, the key names in vcloud-tools-tester) are going to be sufficient to let people know what needs to be set up. In addition, making the variable name more descriptive means that it will be less shareable between tools.

For example, vdc_name_1 in the context of vcloud-launcher:

"Set to the name of a vDC that has at least two OrgVdcNetworks in it. Optionally this vDC should at least two storage profiles."

In the context of vcloud-edge_gateway, this needs to be:

"Set to the name of a vDC that has at least one EdgeGateway device configured with an external network"

In the context of vcloud-net_launcher, this would be:

"Set to the name of a vDC that has at least one EdgeGateway configured"

Trying to encode all that into a single variable name is going to be tricky!