Docs: Describe use cases

The project needs more soft documentation. For example when the framework is or isn't useful.

Typically not useful in early stages of development. Unless it's used for getting some very restricted statistics.)
Not useful for getting data on how it feels to play the game.
Useful for getting quantitative answers to quantitative questions.
Good when you know which questions you want answers to. Less good for free exploring.
Not good if you don't know how to code.
Good to check that some things don't break when you make changes in the game.
Very good for checking well-defined player strategies.
Useful for identifying where the important player choices are.
Useful for analysing the game mechanics.
Useful for making quick but pretty reliable evaluations of large changes in the game.
Very good for using human play testing for experience-focused evaluation, instead of getting numbers on game data.
A risk to be aware of is that models/simulations may have blind spots and in general only answers the questions that are asked -- within the boundaries of the game model.

Itangalo / Bot-Playtesting-Toolkit