Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the baseline is 3. The description adds useful inter-parameter semantics: cost lists replace preset lines, and presets are rough examples, not quotes. It could say more about starting_cash or the distinction between cost arrays, but the schema already covers those.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.