Design a tool result with status, typed fields, evidence, and recoverable error information.
The move: return a contract, not just a sentence. A tool result should be easy for three readers to trust: the model, the application, and the human reviewer. Prose alone makes all three guess. Status Return success, partial, denied, not_found, or error as an explicit field. Do not hide state inside a sentence. Typed facts Use fields the next step can validate. IDs, enums, timestamps, amounts, and booleans should not be buried in a paragraph. Evidence Return where the answer came from. A policy URI, record ID, query timestamp, or source excerpt makes the next action auditable. Recovery When the…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in