Factsheet
Videos
I think Eclipse has come a long way in last the couple of years . I especially really like the native Eclipse CTD environment. The editing experience is really nice and with a lot of nice features, from automated comments and code blocks to really sophisticated search features. Also CDT is making it really easy to start and configure new projects with its build systems. These are not even a scrap of the surface of all the other helpful features for Embedded development that Eclipse offers.
Of course there are some other Eclipse based IDEs from various vendors that can make the development experience to suck. However I would still gladly use these instead of a dumbed down editor. I.e. such an IDE is Vitis from Xilinx (however I think this one could be excused as it is relatively new)
So, I really do not get it why so many of you hate it with such a passion...
All the other answers are more or less true, but miss the point (in my opinion), The download page states it clearly:
Eclipse Standard ... The Eclipse Platform, and all the tools needed to develop and debug it
versus
Eclipse IDE for Java Developers ... The essential tools for any Java developer, including a Java IDE, a CVS client, Git client, XML Editor, Mylyn, Maven integration...
So if your focus is to develop for Eclipse itself, the Eclipse Standard includes all what you need (including the sources of all features and plugins).
If your focus is Java development (not Eclipse plugins), you should start with the Eclipse IDE for Java Developers.
If your focus is Java EE development, it is simpler to start with Eclipse IDE for Java EE Developers and so forth ...
The comparison page could certainly use some links, nevertheless a quick web search will tell you all about those plugin.
For your needs, you might look into the "for Java Developers" package, as it contains WindowBuilder, which let's you define GUIs visually in several frameworks.
(Code Recommenders is also nice, but I've personally found it a bit hit-or-miss)
However, you're fine installing any of the packages either way, since you can always install the plugins you need later on. My recommendation is to simply read about those plugins and make an informed decision on what you should install.