So, since we're talking about CPAN, I'd say that the library and development ecosystem around Tcl is "unsolid" where for Perl it is pretty impressive. It's only relatively recently that Python and Ruby have reached parity with CPAN, even.
Was the phrase, though. I don't think anyone really questions whether CPAN is better than what Tcl had, and you can debate what you like about both languages, but to call Tcl unsolid is not very accurate, in my opinion.
So, I see where you're coming from if speaking only of the language itself. Tcl is a quite nice, well-thought-out, language. It has a few quirks, but so does Perl.
The first two of which would probably be the language design itself and the implementation. I'd rather not argue about the former, and regarding the latter I don't have a lot of experience with Perl, although I've heard that it's gotten better once they awoke out of the post-Perl6 slump. Still, Tcl was always pretty great in that regard.
But as we're talking about the CPAN here, a lot of the alternatives come out short-handed, and Tcl amongst them. I remember the days when you had a different interpreter for every extension...
But you need more than one leg to stand on, and due to its embedded roots and other hysterical reasons, Tcl did a relatively bad job when it came to building a good package library and infrastructure. Which in turn hurt the community, which made for fewer package contributors and so forth.
And once Tk lost most of its importance and languages like Lua appeared...