We have 2 options here:
Easiest is to have your remote peers connecting to your ASA to a dynamic crypto map, then you can configure Reverse Route Injection on this dynamic crypto map and and have the static routes created by RRI redistribued into EIGRP. This will cause that when the tunnel comes up RRI will automatically inject a static route to your device which will be injected to EIGRP. With static crypto maps, I believe these routes will be advertised regardless of the tunnel not being created and completed, but should follow the same principle.