Complexity covers so much, its definition so sprawling, that the phrase has no meaning.
I'd rather focus on the language's real strength, fast, concurrenty, portable computation in very well tooled managed environment with a large number of quality libraries.
I don't want to get into a situation where people think that clojure is the universally 'best' language, which is were certain people in the community are.
That POV horribly damaged ruby's popularity after Rails' rise, and I'd hate to see it happen again to another language.
You're right, though, the definition is sprawling, so I think it makes sense to use smaller more precise words. The good news is we have some of these: Referential transparency, pure functions, immutability, and neologisms such as "complection". These are very useful, meaningful terms.
Software projects are becoming increasingly complex, and multicore concurrency is becoming increasingly important. Immutability and referential transparency are key ingredients in Clojure concurrency so I think the slogan is apt.
I'd say python has a more even distribution in terms of use in varied fields for instance.
Request -> App Server -> Processing -> Response -> End, no state lingering around...
I do understand what you're saying but I believe the era of complex OO with states is declining, at least at web-development level...
There's a big PR problem with environments that have this as a core strength: it's very hard to demonstrate this without a lot of involvement. It's very hard to demonstrate this with a "hello world." sized experience.
With OO, you have to keep track of the state of each object and how each method affects that state. With Clojure, you don't need to be concerned with the guts of a function, just the inputs and outputs. This keeps your mental stack from building up and makes programs easier to understand and debug.