That's really the trick isn't it?
If the IDs are not supported as variables, then off the top of my head I am not sure you could. You have to be able to join the NodeID pulled from the alert to the pool ID. (Since there are multiple pools per nodeID, this really isn't that simple at all unfortunately)
In the clients I have worked with in the past, we would make sure that the email was a descriptive as possible and included the ${NodeDetailsURL} variable. However, that doesn't really help you when you are on-call and off-VPN.
Hopefully the new enhancements to F5 monitoring/reporting/alerting that are being requested through threads like this: https://thwack.solarwinds.com/ideas/1585
If you really want to get your hands dirty, these have definitely served me well in the past:F5 Pollers.UnDP
