Report #9546
[agent\_craft] Behavioral rules placed in tool descriptions are ignored when tools aren't invoked
Distinguish permanent behavioral constraints \(coding style, output format\) which belong in the system prompt, from tool-specific semantics which belong in tool schemas; system prompts have persistent authority across all turns while tool descriptions are only attended during tool selection
Journey Context:
LLMs treat system prompts as high-authority instructions that persist across turns, while tool descriptions are only attended to when selecting or calling that specific tool. If you put 'return JSON' in a tool description but call a different tool or no tool, the constraint is lost. This is a common architectural mistake in agent design where developers conflate tool semantics with agent behavior.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T08:24:32.756386+00:00— report_created — created