Recs.
Updated
Specs
Pros
Pro Multiple front-ends for multiple platforms available
At the moment there is no official Tox client, but a selection of 32 and 64 clients for Windows, OS X, Linux and Android is available.
Pro Distributed
Tox has no central servers that can be raided, shut down, or forced to turn over data — the network is made up of its users.
Pro Number of connections is limitable
Enabling TCP mode will reduce your number of connections. In qTox, this can be done by going to Settings->Advanced->Uncheck Enable UDP. There is likely a homogeneous settings in other apps.
TCP mode connects your traffic through a volunteer server, and obviates you from participating in DHT which mundanely causes you to send marginally of traffic to many different Tox users, engendering the immensely colossal number of connections.
Pro Privacy focused
Tox uses military grade encryption and works completely peer-to-peer.
Cons
Con Not actually decentralized
The closest technical appropriation should be Tox is federated.
Con Toxic community
While the app itself seems quite interesting, the behavior of its fans immediately dissuades from ever trying it out.
Recommendations
Comments
Flagged Pros + Cons
Pro Uses own client instead of badly made, chrome-based clients
A lot of clients (for popular chatting applications) use 'electron', which is known for using much RAM and CPU-Usage. Tox has their own (lightweight) client(s) (see https://wiki.tox.chat/clients ).
Con Decentralized service.
If server goes down may be issue with who you contact.
Out of Date Pros + Cons
Con Early stages of development
Since Tox is relatively new, it has important features missing (like group video) and requires a proper code review before it can be deemed reliable and ready for everyday use.