An assistant returns a shorter announcement and labels it “under the limit.” The form still refuses it. Before asking for another rewrite, check what that limit measures. Words, visible characters, encoding units, and bytes are not interchangeable counts.
Find the rule used by the destination
The example A😀B has 3 visible characters, occupies 4 UTF-16 code units, and uses 6 bytes in UTF-8. JavaScript's string length reports the UTF-16 count. This explains one possible discrepancy; it does not establish how your particular form counts text. Combined accents and more elaborate emoji introduce further differences.
Read the field's guidance and use its counter where available. Check how it handles spaces and line breaks. If you use a separate counting tool, confirm that its rule matches the destination. Avoid pasting private drafts into an unfamiliar public counter simply because it promises a quick answer.
Ask the assistant for a version with some room to spare, rather than a draft perched exactly on a stated maximum. Keep the original text so you can compare meaning after each edit. A model's own count remains a claim to check, not the field's validation result.
Preserve the condition that changes the message
Imagine an event notice saying registration closes on Friday unless all places fill earlier. Shortening it to “Registration closes Friday” removes the earlier cutoff. Tell the assistant which facts must survive: the deadline, that condition, and any essential name or action. Remove repeated phrasing before removing those facts.
Paste the final draft into the intended field and inspect both its counter and preview. Check that the entire ending survived and that punctuation still makes sense. Successful entry is useful evidence, but the application may also validate when saving. If saving is part of your task, confirm the saved text; publishing or sending it is a separate action. Keep the full version when it contains details needed elsewhere.