If it's useful to the caller then it's worth doing (like a unit test helper method), but in this case it's truly an internal thing. A caller should never have to expect these to fire off, unless they've messed with what should be opaque state (in which case, tough).
Sort of like how we don't document Exception as a possible exception unless we're explicitly making that part of the API contract (random things can break internally, but that's not the caller's responsibility).