Choice selects from a controlled set
Choice fits routing, intent, agent selection, policy outcomes, and next actions. Criteria should be mutually exclusive enough that a reviewer can explain why one option won.
Score represents ordered meaning
Score fits urgency, risk, quality, fit, or likelihood when higher and lower values have a consistent meaning. Keep thresholds in application code so business policy stays reviewable.
Noul keeps a binary boundary explicit
Noul is useful for narrow checks where the application needs a bounded signal and confidence. If the real workflow has three outcomes such as allow, review, and block, use Choice instead of hiding review inside a threshold.
One question is easier to evaluate
A small first schema exposes ambiguous criteria quickly. Add more questions only when each answer has a clear consumer and you can test failures independently.