Detect Ambiguity in a Prompt
Surface the ambiguity a model will exploit: vague quantities, hedges, undefined time, open-ended lists, and conflicting instructions — flagged, not fixed.
Overview
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.
Workflow
-
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.
Why This Works
- Ambiguity is where prompts silently fail — surfacing it prevents that
- Signals are grouped by category so the pattern is visible
- Strictness tunes how aggressively borderline terms are flagged
Best for
- Finding interpretation-prone instructions
- Auditing a prompt for vagueness
- Tuning detection with strictness
Not for
- Removing the ambiguity — that's the Prompt Cleaner or Rewriter
- Reformatting the prompt — that's the Prompt Formatter
Use cases
- Finding interpretation-prone instructions
- Auditing a prompt for vagueness
- Tuning detection with strictness