Is My Prompt Clear Enough?
Answer the question directly: a clarity score plus the specific reasons a prompt reads as unclear — vague terms, unstated objective, missing specifics.
Surface the ambiguity a model will exploit: vague quantities, hedges, undefined time, open-ended lists, and conflicting instructions — flagged, not fixed.
Ambiguity is where prompts quietly fail: the model picks one of several readings and you get something off-target. This loads an ambiguity-heavy prompt at strict setting and surfaces every signal — "concise but also comprehensive", "several key points", "a few takeaways", "etc.", "do this soon". Each is flagged with its category and count so you can see how much room for interpretation the prompt leaves. It detects and names the ambiguity; it does not rewrite it away.
Paste a loose prompt
One you suspect leaves room for interpretation.
Set strictness
Strict flags more borderline terms; Lenient only the clearest.
Read the flags
Each ambiguity signal named by category and count.
It files them on different lines. Vague terms land under categories like Vague quantity (several, a few) or Undefined time (soon); a clash between two instructions surfaces as 'Possible contradictions (1): concise / comprehensive'. That contradiction also weighs on the Ambiguity score — the report notes '8 ambiguity flags total; includes 1 possible contradiction' — because it's a tension you resolve, not a word you tighten.
Borderline terms are the ones that move. At Strict, softer signals like the hedge 'try to', the vague quality word 'relevant', or 'a few' get flagged; Lenient keeps only the clearest offenders. The header shows which setting produced the run ('Strictness: Strict'), so re-running at Lenient reveals which of the 8 flags were judgment calls versus unambiguous ambiguity.
That line is a separate diagnostic from the ambiguity flags — it checks six concrete anchors (number, length limit, format, audience, examples, criteria) that pin a prompt down. Scoring 0 of 6 is why Specificity reads 0/100: nothing constrains length, format, or audience. It names the gap; adding the missing anchors in your draft is the fix it points to, not one it writes.
The report ends read-only — 'the prompt is not modified' — then hands off by name: the Prompt Cleaner for redundancy, the Prompt Rewriter to strengthen flagged wording like 'several' or 'soon', the Prompt Formatter to reshape structure. This checker only names each signal by category and count; you pick which flags matter, rewrite them, and run the tightened prompt wherever you work.
Answer the question directly: a clarity score plus the specific reasons a prompt reads as unclear — vague terms, unstated objective, missing specifics.
Diagnose a prompt before you send it: explainable scores for clarity, ambiguity, specificity, and structure, with observations that name where it is vague.
Words like "good", "engaging", and "professional" feel like instructions but specify nothing. Find them so you know where the prompt leaves things open.
A set of before-and-after examples showing exactly what prompt cleanup removes — and what it deliberately leaves alone.
'Make it good', 'be detailed', 'keep it interesting' — vague prompts get vague output. The fix is mechanical: replace every fuzzy word with a checkable instruction.
Formats fuzzy agent instructions into a structured prompt with objective, available tools, constraints, success criteria, and failure handling.
Diagnose a prompt's clarity before you send it — explainable scores for clarity, ambiguity, specificity, and structure. Read-only; it never rewrites.