The idea is that when your dependency graph is too convoluted to look at as an image, it may be useful to explore it interactively. You start by looking at the dependencies of the package (seeing how many other dependencies it pulls in), digging deeper into the ones that seem interesting at the time.

If your dependency graph is simple, I'd recommend tl.eggdeps combined with graphviz instead.