Refactor parsers for better readability

**Problem**
When working with data, the error messages could be more descriptive.

**Suggestion**
Improve error handling and add detailed error messages.

**Context**
This would help with debugging and maintenance.

The issue names parser code but no files, tests, or entry points. Start by locating the parser implementations and their current error-handling paths, then review how failures are reported during data operations. Done means the relevant parser errors provide more descriptive messages and the existing behavior remains understandable during debugging.

Written by the indexing model from the issue text.