Function and tool schema design
Added 2026-07-14 · Last verified 2026-07-14
Expose narrow, intent-level tools with unambiguous names and descriptions, explicit required fields, typed enums and bounds, and no overlapping functions that differ only subtly. Do not make the model invent database keys or hidden defaults: provide lookup tools, use stable external identifiers, and return structured success or actionable error objects. Keep authorization, validation, and side-effect confirmation in the executor, and use strict schema mode where available while testing selection and argument accuracy across realistic prompts.
Useful?
Related notes
Source: The Agent Loop — agent-loop.xyz. Curated in the open knowledge base (CC BY 4.0).