Apply suggestions from SME review

Author: kbatuigas

modules/ai-agents/pages/observability/view-transcripts.adoc

@@ -27,6 +27,8 @@ For basic orientation on agent and MCP server monitoring, see xref:ai-agents:age
 
 Use the timeline visualization to quickly identify when errors began or patterns changed, and navigate directly to transcripts from particular timestamps.
 
+When viewing time periods with many transcripts (hundreds or thousands), the timeline displays a subset of the data to maintain performance and usability. The timeline bar indicates the actual time range of currently visible data, which may be narrower than your selected range.
+
 TIP: See xref:ai-agents:agents/monitor-agents.adoc[] and xref:ai-agents:mcp/remote/monitor-mcp-servers.adoc[] to learn basic execution patterns and health indicators to investigate.
 
 === Search and filter for transcripts
@@ -43,7 +45,7 @@ The search functionality helps you find transcripts by operation names, span typ
 
 ==== Filter by service
 
-Service filtering shows only transcripts from specific agents or MCP servers using the `service.name` resource attribute. See xref:ai-agents:observability/concepts.adoc#cross-service-transcripts[] to understand how transcripts span multiple services.
+Service filtering shows only transcripts from specific agents or MCP servers using the `service.name` resource attribute. See xref:ai-agents:observability/concepts.adoc#cross-service-transcripts[Cross-service transcripts] to understand how transcripts span multiple services.
 
 * View executions from a single agent when multiple are running (service name: `ai-agent`)
 * Isolate MCP server activity from agent activity (service name: `mcp-{server-id}`)
@@ -71,6 +73,10 @@ TIP: Apply broad filters first (time range, service) to reduce the transcript se
 
 Each row in the transcript table represents a high-level agent or MCP server request flow. Expand each parent span to see the xref:ai-agents:observability/concepts.adoc#agent-transcript-hierarchy[hierarchical structure] of nested operations, including tool calls, LLM interactions, and internal processing steps. Parent-child spans show how operations relate: for example, an agent invocation (parent) triggers LLM calls and tool executions (children).
 
+When agents invoke remote MCP servers, transcripts fold together across service boundaries to provide a unified view of the complete operation. The trace ID originates at the initial request touchpoint and propagates across all involved services, linking spans from both the agent and MCP server under a single transcript. Use the tree view to follow the trace flow across multiple services and understand the complete request lifecycle. 
+
+If you use external agents that directly invoke MCP servers in the Redpanda Agentic Data Plane, you may only see MCP-level parent transcripts, unless you have configured the agents to also emit traces to the Redpanda OTEL ingestion pipeline.
+
 Selected spans display detailed information at multiple levels, from high-level summaries to complete raw data:
 
 * Start with summary view for quick assessment