True, tomb provides container encryption. You have a file which holds the
encrypted data and one file which holds the key required to open the
container (called tomb). You are able to burry the key file inside an image
(which is called steganography). I think the "claim" at the cover page about
hidding the tomb file inside a filesystem does not really mean you can
actually hide the file itself. It is more that you can copy the tomb file
somewhere to your directory tree and without the key file it will be pretty
hard to figure out the purpose of the file.
I suggest you simply read the man page yourself and find out what tomb can do
and what it can not do:
http://tomb.dyne.org/manual.html