Tone Checker: Does My Email Sound Rude?

Read it as the recipient would on a bad day. Short commands with no greeting, "just", "obviously", blame words like "again" and "keeps happening", and ALL CAPS are the usual culprits. This tool highlights the exact lines that could sting and gives each a probability, so you know which ones to fix.

It's politeness wrapped around a jab: "per my last email", "as I already mentioned", "thanks in advance for finally…", "no worries if not, I'll just do it myself". The words are courteous but the message is blame or guilt. Saying the actual request plainly is almost always better.

Open with a line of goodwill, turn commands into requests ("could you…" instead of "you need to…"), drop sarcasm and words like "finally" and "again", and explain why a deadline matters instead of implying fault. The rewrite does this for you while keeping every fact and deadline.

Most people read it as mildly passive-aggressive: it says "you didn't read my email" without saying it. If you need to point back, try "Bumping this in case it got buried" or "Following up on the note below", which keep the reference without the edge.

No. Blunt is direct with no padding, and many teams prefer it. Rude adds disrespect: orders, blame or insults. The checker separates them, so a short, clear message gets "blunt", not "rude". Whether blunt is fine depends on the reader, which is why you pick who's reading it.

It's asked to keep every fact, request, name and deadline, and to keep roughly the same length. Read it before you send it: it's a draft, and you know the relationship better than any model does.

Your text is sent to Jev to be judged and to Gemini for the rewrite, then the result is cached anonymously under a hash of the text. It isn't tied to you, and there's no account.