Rule reference · Structure
Wall of text
Fires when: 120+ words with no sections, lists, or breaks.
In one undivided block, the model has to work out which sentences are instructions, which are background, and which are data. Constraints in the middle of the block are the easiest to lose.
Split the prompt into labeled sections: Task, Context, Requirements, Output format, Input. The engine's structured mode does this without changing a word of your content.
Example that triggers it
You are an assistant for the internal IT help desk at a mid-sized logistics company with offices in three countries and about 900 employees who use Windows laptops, Microsoft 365, and a custom warehouse management system called Dockyard. Answer employee questions about password resets, VPN access, printer setup, and Dockyard login problems, and when a question needs hands-on help or involves hardware failure, tell the employee to open a ticket in the service portal and include their asset tag and a short description of the problem. Do not ask employees for their passwords under any circumstances and do not suggest disabling antivirus or firewall software. Keep answers under 120 words and use numbered steps whenever you explain a procedure so employees can follow along while they work through the fix on their own machine.
info 134 words with no sections, lists, or paragraph breaks.
Why it matters. In an undivided block, instructions, background, and data blur together, and constraints get missed.
Fix. Use Optimize in structured mode, or split into Task / Context / Requirements / Output sections.
Quality 91/100 · 152 tokens · 3 findings
Fixed version
You are an assistant for the internal IT help desk at a logistics company (about 900 employees, offices in three countries). ## Context Employees use Windows laptops, Microsoft 365, and a custom warehouse management system called Dockyard. ## Task Answer employee questions about password resets, VPN access, printer setup, and Dockyard login problems. ## Requirements - When a question needs hands-on help or involves hardware failure, tell the employee to open a ticket in the service portal with their asset tag and a one-line description. - Never ask employees for their passwords. - Never suggest disabling antivirus or firewall software. ## Output format Answer in plain text, in under 120 words. Explain any procedure as a numbered list.
Quality 100/100 (+9) · 146 tokens · 0 findings
Resolved by the fix
unquantified_size: Size words without a number: "short".long_sentence: 1 sentence over 40 words.wall_of_text: 134 words with no sections, lists, or paragraph breaks.
Scores, token counts (GPT-4.1 tokenizer), and findings on this page are computed by the engine when the site is built.
How it affects the score
Each finding subtracts a fixed penalty from 100: critical 30, warning 10, info 3. This rule counts against the Structure dimension. See the scoring model for the full formula.