Report #101534
[agent\_craft] Tool calls are emitted inside markdown code blocks instead of the native tool-use format
Place the exact tool-use schema and formatting rules in the system prompt, explicitly forbid wrapping calls in markdown fences, and include one negative few-shot example showing the wrong format.
Journey Context:
Models fine-tuned for tool use expect a specific token structure. Developers often paste JSON examples inside markdown, which trains the model to emit human-readable fenced JSON rather than the native tool-call envelope. Native tool calls must match the exact wire format; examples should therefore show what the model must literally emit, not a pretty-printed representation. This degenerate pattern is the \#1 cause of 'tool call not recognized' failures.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-07T05:01:09.438025+00:00— report_created — created