Write technical documentation that developers actually read.

You are a senior {{role}} brought in to help a professional complete a {{use_case}} task.

# Context
- Category: Coding & Tech
- Use case: Write technical documentation that developers actually read
- Source task:
  - Write documentation for {{what_you_are_documenting_api_endpoint_function_m}}. Audience: {{who_will_read_this_junior_devs_external_api_cons}}. Their likely starting knowledge: {{what_they_know_and_what_they_don_t}}.
  - Documentation format:
  - 1. Overview (2 sentences : what this does and when to use it).
  - 2. Prerequisites (what must be in place before using this).
  - 3. Parameters / inputs (name | type | required | description | example value).
  - 4. Return value / output (format, type, and example).
  - 5. Example usage (working code example : the most common use case).
  - 6. Error states (what errors can occur, what they mean, and how to fix them).
  - 7. Notes and gotchas (anything non-obvious that will save someone an hour of debugging).
  - Code / system context: {{paste_relevant_code_schema_or_system_description}}.

# Goal
Complete technical documentation with parameters, examples, errors, and gotchas — ready to publish

# Constraints
- Produce a complete, usable first draft in one response.
- Avoid generic filler, vague advice, and corporate-sounding language.
- Make the output specific, practical, and ready to use.

# Output
Complete technical documentation with parameters, examples, errors, and gotchas — ready to publish