Report #38257
[agent\_craft] Tool returns a massive JSON object or unformatted string, forcing the agent to waste tokens and reasoning cycles parsing it
Tools should pre-process and format their outputs into markdown or structured, minimal schemas before returning them to the agent context. Strip out null fields, irrelevant keys, and raw boilerplate.
Journey Context:
Agents are text processors. If a tool returns a 500-line JSON with 90% null fields, the agent has to read and reason over all of it. Pre-processing at the tool level \(e.g., returning only non-null fields, converting to human-readable markdown\) drastically reduces token count and cognitive load on the agent. The tool boundary is the perfect place to filter noise.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T18:41:13.617441+00:00— report_created — created