If the shard catalog contains a corrupted persisted DB entry in config.shard.catalog.databases, checkMetadataConsistency will detect it and report a kMissingDatabaseMetadataInShardCatalog error. However, the information provided is vague: we only report the expected dbName, shardId, and dbVersion.

We could enhance this by including the reason why the entry is considered corrupted:

• The document does not match the schema defined in the IDL (reported as a FailedToParse error).

• The document matches the schema, but a field-level validator fails (for example, a corrupted dbName) (reported as a BadValue error).