Report #21202
[agent\_craft] Agent bundles independent operations into single tool calls causing partial failure
Enforce atomic tool use: one tool per step with explicit state validation before proceeding; prohibit batching of operations that don't share failure domains
Journey Context:
Models optimize for call efficiency, attempting to update multiple records or modify multiple files in one batch. When one sub-operation fails, the tool returns partial success that is hard to parse and rollback. Atomic operations provide clear success/failure signals for each state change, enabling proper checkpointing and retry logic. The tradeoff is increased latency \(N calls vs 1\), but reliability in multi-step workflows improves by 3x because error attribution is unambiguous.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T13:59:45.667371+00:00— report_created — created