Simplify Text
readability_simplify_textSimplify English text into plain language by splitting long sentences and replacing formal vocabulary. Confirm readability improvement with Flesch Reading Ease scores before and after.
Instructions
Rewrite English text in plainer language: breaks overly long sentences at natural clause boundaries and swaps common bureaucratic vocabulary ("utilize" -> "use", "prior to" -> "before") for plainer equivalents. Also reports the Flesch Reading Ease score before and after, so you can confirm the rewrite actually helped.
Use this before sending a reply, document, or notice to a user who may benefit from plainer language -- including as a self-check step for an agent's own drafted output.
Args:
text (string, 1-20000 chars): The English text to simplify.
response_format ('markdown' | 'json'): Output format (default: 'markdown').
Returns: For JSON format: { "supported": boolean, // false if text contains non-Latin script (English-only feature); simplifiedText equals the input unchanged in that case "simplifiedText": string, "changeCount": number, // total words/phrases substituted "changes": [ { "start": number, "end": number, "original": string, "simplified": string } ], // offsets index into simplifiedText "truncated": boolean, // true if changeCount exceeds 50 (only the first 50 are listed) "fleschReadingEaseBefore": number|null, "fleschReadingEaseAfter": number|null }
Examples:
Use when: "Make this notice easier to read" -> pass the notice text
Use when: checking whether your own drafted reply is needlessly complex before sending it
Don't use when: the text is not primarily English -- word substitution is skipped for non-Latin script (Arabic morphology in particular makes naive word-swapping unreliable) and the text is returned unchanged, with supported=false
Error Handling:
Returns an error if text is empty or exceeds 20000 characters.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | The English text to simplify, e.g. a draft reply before sending it to a user. | |
| response_format | No | Output format: 'markdown' for a human-readable summary or 'json' for structured data. | markdown |