Hi b.kodan,
The TCP monitor just tries to establish a TCP connection to the individual pool members. If the 3-way handshake completes the monitor will be marked as "successful".
The HTTP monitor will also establish a TCP connection to the individual pool members. And right after send an additinall HTTP-Request over TCP-connection. If the monitor receives a HTTP-Response (whatever the response will look like) the the monitor will be marked as "successful".
Note: The recommended approach is to use a tailordered HTTP-Monitor for HTTP-Pools. on this way you can define the exact HTTP-Request matching your application logic and the expected HTTP-Response from your "healthy" application (e.g. 200 OK, certain HTML-contents, etc.).
Cheers, Kai