// notes from an old coder -- php, databases, and the occasional rant
A tool that both writes a row and sends email is hard to retry and hard to audit. Split side effects so the agent can recover mid-flight.
Tool JSON schemas should be as strict as an HTTP contract: required fields, enums, and no extra properties. Loose schemas produce unusable arguments.
When the model must pick a tool and fill JSON arguments, a low temperature reduces schema drift and invented function names.
Put non-negotiable rules in the system (or developer) message so they survive noisy user turns. The model treats that channel as the contract for the whole session.
// showing 1-4 of 4 posts • page 1/1