Choose the task API and evaluate its specific failure mode.
1. Rewriting versus correction
A rewrite can alter tone and phrasing; proofreading aims to fix errors. Preserve names, numbers and domain terms in both cases and give users a comparison before replacement.
2. Image descriptions
Descriptions are generated interpretations, not verified facts. Handle ambiguous scenes and avoid assuming identity or intent from appearance. Respect image preparation and capability requirements.
3. Accessibility behavior
Generated descriptions can assist users but should not hide existing labels or controls. Mark them as generated and preserve a manual description path.
Worked scenario
A rewrite makes a polite request sound like a firm commitment. Grammar improves but the business meaning changes.
Apply it
Compare proofreading and rewriting on the same messages, then evaluate image descriptions on clear and ambiguous scenes.
Check your understanding
You select an API based on the required transformation rather than treating every task as generic prompting. Explain the decision and show evidence from your implementation or design. If you cannot demonstrate it yet, revisit the relevant section before continuing.