A model profile should be useful without pretending model choice is one number. It needs identity, sources, capabilities, constraints, deployment notes, and practical fit.
| Section | Required fields |
|---|---|
| Overview | Provider, release date, model family, modalities, license/access, context window, deployment options. |
| Capability profile | Reasoning, coding, math, multimodal, tool use, latency, cost, open/closed weights. |
| Evidence | Benchmarks, source dates, reviewer status, known contamination or comparability caveats. |
| Use cases | Best fit, avoid when, implementation notes, related models, known weaknesses. |