PYTHON-5993 Clarify the operation_telemetry docstrings

Carries the wording from PR 1 forward and corrects it for the behavior
this branch adds: both cursor types pass a span now, and what one covers
is a single caller-driven getMore rather than a run of them.

Author: blink1073

pymongo/asynchronous/mongo_client.py

@@ -1912,7 +1912,8 @@ async def _run_operation(
         :param address: Optional address when sending a message
             to a specific server, used for getMore.
         :param operation_telemetry: The calling cursor's operation span, or None,
-            so this send's command spans nest under it.
+            so this send's command spans nest under it. Covers one caller-driven
+            getMore, or a whole API call that drains the cursor itself.
         :param reuse_current_span: Create no operation span at all and leave the
             ambient span in place as the parent for this operation's command
             spans. Mutually exclusive with ``operation_telemetry``. Defaults to

pymongo/synchronous/mongo_client.py

@@ -1907,7 +1907,8 @@ def _run_operation(
         :param address: Optional address when sending a message
             to a specific server, used for getMore.
         :param operation_telemetry: The calling cursor's operation span, or None,
-            so this send's command spans nest under it.
+            so this send's command spans nest under it. Covers one caller-driven
+            getMore, or a whole API call that drains the cursor itself.
         :param reuse_current_span: Create no operation span at all and leave the
             ambient span in place as the parent for this operation's command
             spans. Mutually exclusive with ``operation_telemetry``. Defaults to