Capture tool call arguments and results in OpenTelemetry spans

[aneez004]

Problem

Tool call spans currently do not capture input arguments or output results. This data is only visible in application logs at DEBUG level, making it nearly impossible to correlate traces in observability dashboards with the actual user queries or actions that triggered them. Observability platforms are not able to display input/output in tracing dashboards.

What's missing from spans:

• Tool call arguments
• Tool call results
• GraphQL query and response data

Example screenshots from Langfuse tracing dashboard

Expected Behavior

Tool execution spans should include attributes for:

1. Tool call arguments / GraphQL query
2. Tool call result / GraphQL response