docstring

Document a Python module and its classes using Google-style docstrings following project conventions. The class name is provided as an argument.

## Instructions

1. First, find the class in the codebase:
   ```
   Search for "class ClassName" in src/pipecat/
   ```

2. If multiple files contain that class name:
   - List all matches with their file paths
   - Ask the user which one they want to document
   - Wait for confirmation before proceeding

3. Once the file is identified, read the module to understand its structure:
   - Identify all classes, functions, and important type aliases
   - Understand the purpose of each component

4. Apply documentation in this order:
   - Module docstring (at top, after imports)
   - Class docstrings
   - `__init__` methods (always document constructor parameters)
   - Public methods (not starting with `_`)
   - Dataclass/config classes with field descriptions

5. Skip documentation for:
   - Private methods (starting with `_`)
   - Simple dunder methods (`__str__`, `__repr__`, `__post_init__`)
   - Very simple pass-through properties
   - **Already documented code** - If a class, method, or function already has a complete docstring that follows the project style, do not modify it. A docstring is complete if it has:
     - A one-line summary
     - Args section (if it has parameters)
     - Returns section (if it returns something meaningful)
   - Only add or improve documentation where it is missing or incomplete

## Module Docstring Format

```python
"""[One-line description of module purpose].

[Optional: Longer explanation of functionality, key classes, or use cases.]
"""
```

Example:
```python
"""Neuphonic text-to-speech service implementations.

This module provides WebSocket and HTTP-based integrations with Neuphonic's
text-to-speech API for real-time audio synthesis.
"""
```

## Class Docstring Format

```python
class ClassName:
    """One-line summary describing what the class does.

    [Longer description explaining