# Schema Review Checklist

## Before you approve
- Is the task really a data-return task instead of a tool-action task?
- Are all required fields explicitly named?
- Are types explicit instead of implied by prose?
- Are enums used where the values should be closed?
- Are nullable and optional fields clearly separated?
- Is there a visible failure path instead of silent fallback?
- Can a downstream system validate this without guessing?
- Does the schema avoid copying large free-text blobs unless truly needed?

## Failure handling
- What happens if one field is missing?
- What happens if one field is malformed?
- What happens if no answer should be returned?
- Does the model have a way to say "insufficient evidence" or "cannot comply"?

## Downstream safety
- Could this output accidentally trigger an action?
- Could a parsing success still hide a semantic failure?
- Is there a human review step for high-risk outputs?

## Final call
- Pass / conditional pass / fail
- Notes:
