Report #46253
[synthesis] Agent fails to call tools correctly when parameters require nested JSON objects or complex schemas
Flatten all tool schemas to single-level parameters wherever possible, using stringified JSON only as a last resort, and provide explicit examples of the exact parameter format in the tool description.
Journey Context:
LLMs struggle to generate valid nested JSON for function parameters, often omitting brackets or hallucinating keys. This leads to tool call failures or, worse, passing malformed data that causes unexpected API behavior. Flattening the schema \(e.g., parent\_child\_key instead of parent: \{child: key\}\) significantly reduces the cognitive load on the LLM and increases tool call reliability, preventing the chain-of-reasoning from derailing on syntax generation.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T08:06:46.618429+00:00— report_created — created