True to a certain extent, but I you *do* have to take some things for granted and can't list everything needed to use this function in the doctring.
* You do need to know returns a dict.
* You might want to know what you get in this dict (sth. that is still not possible without trying some examples).
* You do need to know that a useragent needs to be set before using the function
* You do need to know what kind of query parameter that is (though you might guess just putting any strings there will work, althoug the information that this isn't just searched in the artist field is "key").
* You do need to know what limit and offset do (something I only explain in the [usage](https://python-musicbrainz-ngs-jonnyjd.readthedocs.org/en/doc_changes/usage/#browsing), but might need extra lines in the API section).
* You do need to know what the `strict` switch actually does.

Most of these things were previously missing. Possibly people didn't want to write that to one docstring, copy it to others, change it and copy it again. The whole point of the documentation is to point out the right things at the right places.
Having each of the functions "self-contained" is not the thing you want to go for when you have lots of functions that mostly work the same.


So please tell me what short information should be added to each docstring without making the the documentation too redundant to maintain and/or read ;-)
It might be nice to have a very short summary in the docstring, but I haven't found anything yet that doesn't seem too obvious ("searches for artists" D'oh) or too generic/redundant ("see `searching`_").