-Nothing prevents you from changing it, but be aware that there lurk dangerous side effects.
-For example, it may rightfully be readonly if the key was a bareword.
-You can get a copy instead by passing C<< copy_key => 1 >> to L</wizard>, which allows you to safely assign to C<$_[2]> in order to e.g. redirect the action to another key.
-This however has a little performance drawback because of the copy.
+Note that C<$_[2]> may rightfully be readonly if the key comes from a bareword, and as such it is unsafe to assign to it.
+You can ask for a copy instead by passing C<< copy_key => 1 >> to L</wizard> which, at the price of a small performance hit, allows you to safely assign to C<$_[2]> in order to e.g. redirect the action to another key.
+
+=back
+
+Finally, if C<< op_info => $num >> is also passed to C<wizard>, then one extra element is appended to C<@_>.
+Its nature depends on the value of C<$num> :
+
+=over 8
+
+=item *
+
+C<VMG_OP_INFO_NAME>
+
+C<$_[-1]> is the current op name.
+
+=item *
+
+C<VMG_OP_INFO_OBJECT>
+
+C<$_[-1]> is the C<B::OP> object for the current op.