Report #103844
[agent\_craft] Model answers in plain text instead of emitting tool calls
Put tool schemas at the end of the system prompt, after task framing; use a hard delimiter like between plan and call; and explicitly tell the model not to explain before calling a tool when latency matters. This forces a clean mode switch from reasoning to action.
Journey Context:
Most agents put tool definitions first, which the model treats as preamble and starts answering before calling. Anthropic and OpenAI docs place tool definitions in system context, but ordering inside it matters: task intent first, schema second. A competing 'helpful assistant' persona often overrides tool instructions. XML-wrapped tool sections work but delimiter tokens are cheaper and easier to parse. The real win is separating 'decide' from 'call' so the parser never has to strip friendly filler.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-13T04:48:16.098695+00:00— report_created — created