What are the downsides of running a Physical Only Database Integrity Check job

I am unable to find an article yet, that is able to clearly help my understanding of the risks I run by running my Ola Hallengren DatabaseIntegrityCheck job with PHYSICALONLY parameter on our large databases. There is no mention of a FULL check being done: [https://ola.hallengren.com/] > Run Integrity Checks of Very Large Databases The SQL Server > Maintenance Solution has been designed to do integrity checks of very > large databases. In the DatabaseIntegrityCheck procedure you can > choose do the checks on the database level, the filegroup level, or > the table level. It also supports limiting the checks to the physical > structures of the database: > > EXECUTE dbo.DatabaseIntegrityCheck @Databases = 'USER_DATABASES', > @CheckCommands = 'CHECKDB', @PhysicalOnly = 'Y' These checks are limited to checking only the physical consistency i.e. that all data is present and can be read. Is someone able to clarify for me please, or point me to an article that can clearly help me with exactly what are those logical checks that this PhysicalOnly check ignores, and what risks could be associated with ignoring the logical checks or doing a FULL check less frequently