Clustered indexes are also known as Index Organized Tables (IOT). Which is a more descriptive name.
The primary key index IS the table. So to get a record you only need to search the index. The DB doesn't need to get a reference to the RowID to fetch the data.
So it's very fast when using the primary key index.
But as the nature of a BTree index is that it's self balancing you don't have a RowID on the record. This means that secondary indexes needs to reference the primary index to get a record. So using secondary indexes is slower than on a normal table.
Another drawback is that ALL fields will be in the index, so it's unfit for using whenever you have more than one field that's not actually used in the index.
It also means that IOTs are unfit for using when you have fields with (largely) varying sizes, such as large varchar fields or binary data fields.
So usage is quite limited, I'm more or less only using them in junction tables that's used for one direction joins only.
Some well written info
here[
^].