How do Dask-worker's get keywords?

If I ask for my workers to get a certain amount of memory or CPU usage, how do Dask workers learn about these limitations? Are we relying on the Dask workers to inspect their local VM and pull CPU counts and memory limits from there?

I ran into this problem with the dask-ssh rewrite, where I wanted to convert a large amount of Python keyword arguments, like `nthreads=4` into CLI keywords, like `"--nthreads 4"`. I'm wondering if this project faces a similar problem.