Type a name into Wikipedia's mobile app and a sentence appears under the title before the article loads. The same line shows up in the desktop search-results dropdown, in the Wikipedia API that powers voice assistants and third-party apps, and — on some searches — in the information panel next to a Google results page. That sentence is the short description, and almost no one outside the editing community sets out to write one on purpose.
It lives in one of two places. Most articles carry a short-description template at the very top of the wikitext, a single line an editor typed by hand. Where that template is missing, the software falls back to the description stored on the article's linked Wikidata item — a separate database, maintained by a smaller and largely different set of editors, with its own history and its own disputes. A firm that has read every revision of a client's Wikipedia article can still be surprised by what a phone search turns up, because the two descriptions aren't always written, or even noticed, by the same people.
A short description exists to help a reader tell the subject apart from others that share its name or might be confused with it; it is not meant to serve as a definition, a summary of the article, or a tagline.
In practice that means a short description answers one question only: what kind of thing is this, well enough to separate it from everything else that might share its name. "American jazz pianist." "British multinational bank." "Village in Himachal Pradesh, India." None of these sentences argue a case. They sort.
Firms drafting their own first pass tend to reach for the same register: "award-winning global consultancy," "leading provider of enterprise software." Either survives a few hours, sometimes a few days, before an editor doing routine maintenance on short descriptions trims it to "American management consulting firm" or "software company." The edit summary is usually one word — promotional. Nothing about the company's real record is in dispute; the sentence was just doing a different job than the one it was given.
Correcting a short description that's outdated, wrong, or carried over from an abandoned Wikidata edit follows the same path as any other change on a page with a declared conflict of interest: propose the replacement on the talk page, name what changed, and let an uninvolved editor make the edit. The request that gets accepted fastest reads like a caption, not a pitch — five to eight words, no adjective standing in for evidence.
Checking the article's prose alone won't catch it. The short description and the Wikidata description are two separate sentences, kept by two separate communities, and only one of them necessarily sits inside the page a firm thinks it controls. Read both before reporting that something is wrong — and before promising a client that fixing one will change the other.
