Lots of comments here:
Speedbird22, I think that the abbreviated call that you have been taught is about right. You can always argue with individual words, but the basic structure is fine. Much better the the full TR PACER
Secondly, the word "Inbound" is very useful. If you call a potentially busy field, particularly if there is IFR traffic around as well, the controller doesn't want your full (even abbreviated) call first time he hears from you. Instead try "Leeds Approach G-ABCD inbound". The controller will then grab a strip and a pen and call you back for "your details", at a time which is good for him, and you won't end up repeating yourself or blocking that 757 from establishing on the Localiser.
Inbound also gets around the uncertainty as to whether you need landing/airfield or other details, so works well for FISOs and A/Gs
Foghorn: The initial Call for transit is a good idea that seems to work well at Luton. The fact that 9 times out of 10, they route you through the overhead does not mean that you should necessarily anticipate that in your call. I would just stick to telling them that you want "VFR" or "IFR" transit enroute to Cranfield because then they know what they are dealing with. As an additional stylistic point, you and I both know that WOBURN is a VRP for Cranfield. Now that Luton approach are in West Drayton, the chances of finding anybody who knows or cares what Woburn is are becoming more remote.Too much information is a bad thing. Just let them clear you enroute once you've left the zone. They don't care whether enroute means to WOBURN, STEWARTBY or the CIT.
Incidently, watch that you don't bust Stansted's airspace or Panshangers ATZ as you route direct LAM to Luton's overhead. This is a common enough error to be worth pointing out
-2Donkeys