Add docstring section

Author: voetberg

docs/developer/style_guide.md

@@ -248,3 +248,45 @@ tools/run_pyright.sh generate {report_output_path.json}
 ```
 The first action will raise an error if your commits introduce more un-annotated types than it solves,
 and the second ensures the added types are consistent with the rest of the codebase.
+
+
+# Docstring Style 
+Python Client documentation is autogenerated from docstrings, and need to follow a defined style. 
+Client Docstrings use the `numpy` style, a [description of the style can be found here](https://numpydoc.readthedocs.io/en/latest/format.html)
+and [an example can be found here](https://www.sphinx-doc.org/en/master/usage/extensions/example_numpy.html). 
+
+Notably, docstrings should **not** explicitly include types, as they are automatically added from the type annotation. 
+
+A basic example can be seen below: 
+
+```python
+
+ def function(param1: int, param2: Optional[str] = None) -> None:
+    """
+    The function description
+
+    Parameters
+    ----------
+    param1
+        The first parameter
+    param2
+        The second parameter
+
+    Returns
+    -------
+    None
+        Nothing is returned
+
+    Raises
+    -------
+    TypeError
+        If something goes wrong
+
+    
+    Examples
+    --------
+    >>> function(1)
+    >>> function(1, "one")
+    """
+
+```