When a programmer designs a library, he generally has use cases in mind. So she plays around with a procedural and object oriented interfaces, and see what feels more natural, and what leads to the least code duplication.

If a procedural interface ends up passing all the same information to each routine call, it's a bad design, and the information should be stored in an object instead.