I like to think of some of these services as "pairs" or "groups" (regardless of the dependencies) and set their start state equal for all of them. You can learn something more about the groups in the dependencies tab, but it's not always accurate.
For example, Lanmanworkstation is kind of a sibling of Lanmanserver. They both are used in MIcrosoft Networking (file and printer sharing). It would make no sense to have one started and the other not (except in some marginal high-security situation, where you maybe would want to hide something from your users/slaves). Their third sibling is Browser. Netbios over TCP (or whatever it's name was, I'm not on XP right now) is also their relative. If you use file/printer sharing, you enable them all and have no headaches, it's that simple.
Another example is ALG. It serves (rough approximate explanation) to punch holes through Windows Firewall (legitimate ones, although holes can be punched in WF very easily, and every other aplication does that even without it). So it would make no sense to use ALG without WF, while the other way around... I have not tested. Probably could do without, but it always bothers me to see it manual and started, so I let it have it its way and set it to automatic - on computers where I use WF, which is very rare.
Again, from memory, another group is Com+ Event System, System Event Notification and... I forgot which one, maybe WMI (but WMI is also associated with some others).
Remote Access Connection Manager and Remote Access Auto Connection Manager (that was easy
), but also Telephony. They usually start each other.
SSDP Discovery and/or Universal Plug and Play Device Host - if you use UPNP. By the way, even if you don't, one of them always gets started by itself no matter what, so I must set it to disabled.
And so on and so on... Ask about any service, I have investigated most of them and roughly know what they are for.