<tangent>
Well, if that's how you write the documentation, then no, it's not useful to add. However, IMHO as a programmer, you don't put into a manual "our application is bullet proofed against bad data," but you do put into the manual what your product does do (skips to the next track), especially if it's non-obvious, when it encounters bad data (corrupted, or non-music files).

A car owner's manual would certainly say "If you flip the switches in the wrong order, all switches are reset to the off position to prevent overloading the electrical system."
</tangent>

That said, not all documentation is end-user documentation. Internal specifications, or even the comments surrounding the code, if either are available, could satisfy the requirements.