How strict should tool schemas be? Enums prevent chaos but freeze every new value
Ctbhatia · reddit · 2026-10-15
A short but classic agent-tool design question: type a status arg as a plain string and you'll eventually get "in progress", "In Progress" and "wip" for the same thing — and the tool just takes it. An enum fixes that, but every new status becomes a schema change. The author asks: enums everywhere, or only after a field has already bitten you?
More from coding & agent
- Claude cut a 2.6-hour video export to 20 minutes — but only after being told to rebuild the server — byhewar · 2026-10-23
- 3 flight-booking rules my AI agent checks that I'd never do by hand — Efistoffeles · 2026-10-23
- OpenJet claims Qwen3.8-27B coding runs 1.9x faster than llama.cpp on one RTX 3090 — JeremyCMorgan · 2026-10-23
- Building an autonomous SEO agent in Hermes with three skills: programmatic pages, Keywords Everywhere, DataForSEO — EXM7777 · 2026-10-23
- Building a sports betting AI agent with onchain execution and human approval by default: architecture and lessons — Dry-Comfortable-2678 · 2026-10-23
- How do you audit AI agent decisions in regulated workflows? A field survey — Ok_Way_1993 · 2026-10-23