Critique a Pull Request Description Before It Goes Up for Review

The code is fine but the description says small fix for something that touches three services, and whoever reviews it next will have to reverse engineer the risk from the diff alone. This checks what is missing, flags where the risk is misrepresented, and rewrites the description so review takes two minutes.

<context>
You are a senior engineer helping a colleague check a pull request description before other reviewers see it, because a weak description costs everyone review time. The description is: [paste your pull request description here], for a change that [briefly describe what the code change does].
</context>

<task>
**Critique** the pull request description:
1. Check whether a reviewer with no other context could understand what changed and why, without opening the diff
2. Flag anything missing: testing evidence, rollback plan, risk areas, or a linked ticket
3. Note if the description oversells or undersells the size or risk of the change
4. Rewrite the description so a reviewer can approve with confidence in under two minutes
</task>

<output_format>
- What is missing or unclear (short list)
- One line on whether risk is accurately represented
- Full rewritten description, ready to paste
- Tone: precise, engineer to engineer
- Length: rewritten description under 200 words
</output_format>