Behavior of (ERROR 'TYPE-ERROR)

[pamoroso]

Suppose you evaluate this at a XCL Exec:

2/5> (ERROR 'TYPE-ERROR)
Arg not a NIL
NIL

2/6> (ERROR (MAKE-CONDITION 'TYPE-ERROR))
Arg not a NIL
NIL

Is this the expected behavior? I assumed the condition type TYPE-ERROR would be mentioned somewhere like SBCL does:

This is SBCL 2.5.10, an implementation of ANSI Common Lisp.
More information about SBCL is available at <http://www.sbcl.org/>.

SBCL is free software, provided as is, with absolutely no warranty.
It is mostly in the public domain; some portions are provided under
BSD-style licenses.  See the CREDITS and COPYING files in the
distribution for more information.
* (error 'type-error)

debugger invoked on a TYPE-ERROR in thread
#<THREAD tid=77279 "main thread" RUNNING {1200030003}>:
(A UNBOUND-SLOT was caught when trying to print *DEBUG-CONDITION* when entering
the debugger. Printing was aborted and the UNBOUND-SLOT was stored in
SB-DEBUG::*NESTED-DEBUG-CONDITION*.)
(CELL-ERROR-NAME SB-DEBUG::*NESTED-DEBUG-CONDITION*) = SB-KERNEL::EXPECTED-TYPE

Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
  0: [ABORT] Exit debugger, returning to top level.

(SB-INT:SIMPLE-EVAL-IN-LEXENV (ERROR (QUOTE TYPE-ERROR)) #<NULL-LEXENV>)
0] 

[pamoroso]

The error message is a bit clearer if I call ERROR with additional arguments but it still does't mention the condition type:

2/7> (ERROR 'TYPE-ERROR :DATUM 'ASYMBOL :EXPECTED-TYPE 'FLOAT)
Arg not a FLOAT
ASYMBOL

[pamoroso]

Never mind, the condition type is shown as the title of a break window when invoked.