I think most of your beefs are, "what are the types of things", but Python wasn't very type savvy until pretty recently, so stuff was generally very implied. If you wanted type info you had to explicitly notate it in docs, which was kind of laborious and not easy to make perfectly accurate, so most people didn't do it (also it works against duck typing, like must this be an `int` or just something that supports `__add__`?). It's maybe also worth saying that if you click in the `time.time()` link in the 1st sentence of your 2nd example you'll pretty quickly see many indications that the return type is a float.

I'm (maybe this goes without saying) a big fan of the Python docs. They make simple things easy by covering the 80% use cases really well, and for the rest they link source code up at the top. Django does this too which I really appreciate. I think you generally learn to use the affordances of the internet and browsers (cafile site:docs.python.org, ctrl+f) with all websites like, I mostly don't want websites reimplementing that stuff--usually worse--for me.

I would contrast it with the Python gRPC docs [0] which are a lot more type-savvy but don't really very much context about what the methods and such do. Like I've read [1] about 4 times and I don't understand it any better than after the 1st read.

IDK all I'm saying is there's more to it than just type information. Communicating technical information to people is really involved.