The resolution plays out very differently. "Hostile action" covers any display of hostility, including drawing your sword and preparing to strike (behavior that may be inferred in the "Attack" action when taken in combat.) The readied spell is one which can interrupt the attacker, so casting it before the ranged or melee attack is made is important. If the spell succeeds, the planned ranged or melee attack will not be made. If the trigger is "make an attack," however, the attacker gets to make the attack before the spell is released. If the attacker doesn't have the extra attack feature, then no attacks will be interrupted by the spell this turn, and if the caster loses concentration before the attacker's next turn no attacks will be interrupted by the spell at all.
"Hostile action" is a convenient shorthand my group has come to use instead of "any indication that the target is preparing to make a weapon attack or cast a spell."
I wasn't focusing especially on the "hostile action" bit as that did not seem relevant to the work your example was doing.
My point is that the example plays out no differently whether the trigger is "hostile action", "make an attack", "take the attack action", etc. Whichever wording is used, the in-fiction trigger is the drawing of a sword, the nocking of an arrow, or whatever it might be.
I make an attack connotes that sort of thing just as does
I take the attack action; and if a character can ready an action that will be triggered by
taking the attack action then it will likewise be triggered by
making an attack.
5e has the standard difficulty of RPGs in expressing its rules for interrupts while trying to use language that straddles the fiction and the mechanics in a relaxed fashion. (CCGs have less of this issue because they have no fiction in the relevant sense.) You can see an example of this in the wording of the Shield spell. Consider the fiction of that spell: does it allow the magic to travel back in time? No - rather, the fiction is that the caster sees the sword coming, or the arrow flying, or whatever it might be, and conjures a magical barrier into existence. To ensure that, mechanically, the shield spell is resolved before the making of the attack (the d20 roll compared to AC) is resolved, the spell includes express wording that the AC bonus applies to the triggering attack even though, at the table, the d20 may well have been rolled before the casting of the spell is declared.
The rules for readied actions (Basic PDF, p 72) state that "When the trigger occurs, you can . . . take your reaction right after the trigger finishes". Which
in a CCG would be bad for interruption. But those rules also state that "you decide what perceivable circumstance will trigger your reaction" - in other words, triggers are defined in terms of the
fiction, not the
mechanics (I take it as obvious that
perceivable here means
by the character, not
by the player), and hence if you want to interrupt someone who
takes the attack action or
makes an attack or
takes a hostile action your perceptible trigger is drawing the sword or nocking an arrow or whatever - a fictional state of affairs - and not
resolving a declared action - which is a mechanical state of affairs.
But in any event, in thinking about these peculiarities of how RPGs handle interrupts, it's clear that
making an attack and
taking an attack action are not interestingly different. (It also reinforces the fact that 5e is not a "rules light" or "fiction first" game, at least where combat is concerned, as it has all these mechanical features of turn-based resolution that are closer to a CCG or boardgame even than to a traditional wargame, let alone a fiction-first RPG.)