I think you'll find some of the answers within the UK's SRD (Standard Routing Document). This is available freely via the AIS website.
It's not a pilot friendly document, nor some would argue does it need to be. It does however allow Nav/Ops departments to see level restrictions upon certain inbound/outbound routes from the UK. My company uses this, builds the early descents into the PLOGS and so we have adequate fuel. Encourage yours to do the same........
I pushed heavily for the publication of all this years ago. The problem with places like Leeds, Midlands Group airfields etc, is that many of the descent profiles are before the start of the STAR. There is no easy place to put the expected descent restrictions on such arrivals.
I do believe there is an argument for extending STARS for some airfields beyond their current starting point, and hence including descent data. RT loading could also be reduced.
eg: BB arrival through S19:- typical 1st call response " ABC123 goodafternoon, maintain FL350, routing AVANT, MIDHURST,OCKHAM, HEMEL, GROVE 1C Birmingham."
Extend the STAR back to HEMEL. Include the EXPEXTED descent data and RT now "ABC123 goodafternoon, maintain FL350, routing AVANT GROVE 1C Birmingham."
Valuable RT time saved on both ATC transmission and aircraft readback!
30W