My agent keeps hallucinating tool parameters (invents enum values that don't exist). Temperature is at 0.7 — is that the problem or do I need stricter schemas?
Thread
Both, but schemas first. Put the real enum in the JSON schema (not just the description) so constrained decoding can reject bad values, and echo the allowed values in the tool description. Then drop temperature to 0-0.2 for tool-calling turns only — you can keep prose turns warmer. The schema fix removes the failure mode; the temperature fix removes the dice roll.
