Metric definitions in receiver_metrics.md are insufficient and unclear

[mink0119]

Describe the bug

The metric descriptions provided in the following documentation are insufficient for understanding what the metrics actually represent:

https://github.com/f5devcentral/application-study-tool/blob/v0.9.6/pages/components/otel_collector/receiver_metrics.md

Most descriptions simply restate the metric name in sentence form and do not explain:
What is being measured,

To Reproduce
Steps to reproduce the behavior:

Locate the following metrics:

f5_virtual_server_clientside_connection_slow_killed_total
f5_virtual_server_ephemeral_connection_total
f5_profile_tcp_accepts_total
f5_profile_tcp_connections_total
f5_profile_tcp_tx_rexmits_total
f5.pool.queue_age.average
f5.pool.queue_age.recent_max
f5.profile.fastl4.rx_badsums
f5.profile.fastl4.rx_badpkts
f5.profile.fastl4.rx_unreachs

Read the provided descriptions.

Expected behavior
Each metric should have a clear and operationally meaningful explanation, including:

Typical use cases (capacity, troubleshooting, performance, security)
Any relevant BIG-IP internal counters or tmsh show equivalents