Type annotation appears before the type’s simple name

[Paul Benedict]

Regarding examples:
1) Map. at NonNull Entry
2) java.util. @Marker List
vs.
1) @NonNull Map.Entry
2) @Marker java.util.List

Can someone please explain why the EG prefers putting the type
annotations inside the qualified name (right before the simple name)
rather than at the beginning? Is there a strong benefit to the
developer?

It strikes me odd that breaking up a qualified name is the preferred
approach. It seems to go against the 99% usage in the rest of the
spec.

Thank you!
Paul