I’d like to suggest FME exposes the Database Spatial Tolerance in the Feature Information window, alongside the projection, dimension, min/max extents etc.
This information is critical when understanding spatial filtering, and can account for features being inside or outside specific areas of interest when using a spatial filter within a Reader/FeatureReader, and gives context to the features being retrieved.
In Oracle, this would mean reading the sdo_metadata table in the database, but other database types would require differing tables to be read.
It would also be useful for FME to perform a simple calculation using the projection and the tolerance together, and write a warning message in the translation log if the tolerance (on the ground) is of a large distance - especially useful when spatially filtering data.
Thanks,