Report #54265
[research] Unattributed token costs make it impossible to optimize expensive agent tools
Tag every LLM completion span with the specific tool/sub-agent name and task type, enabling cost attribution per capability rather than just per model.
Journey Context:
Standard observability tracks total tokens per API key. In an agentic workflow, a single research tool might consume 80% of tokens via massive context injection, while a formatting tool uses few. Without tagging spans with the tool name, you cannot identify which specific agent capability is driving costs, making optimization blind.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T21:34:53.843951+00:00— report_created — created