Have you ever noticed how a game designer's description of something in a game is often noticeably optimistic? That mythical weapon you found that melts your opponents actually only removes a third of your enemy's hit points, at best. The spell you've just learned that banishes an evil creature actually only is in effect for a few turns. The powerful character you've just bought a miniature for is actually weaker than the orcs he's famous for destroying in the lore. Game designers often aren't wrong when they describe in-game items this way, they're just speaking to you from a temporally advanced perspective. Your game tells you what a component is meant to become after it's gained experience, which can guide how you use that component in the game.
A game designer has the ability to view any given game component from its fully realised state, and so speaks about it as if it were fully developed. They're druids, essentially, who speak of acorns as oak trees. That powerful weapon will melt your opponents, at least after you've levelled up enough to get that kind of damage output. It's not wrong, it's just premature from a certain perspective. As a player of games, I often think of game designer descriptions of game components as aspirational, and I often play my games using that aspiration as in-game motivation.
What this means in practise, though, is that sometimes you get a thing in a game and it just doesn't behave or feel like what the game "sold" to you. In Warhammer 40,000, for example, a Space Marine is described as a powerful warrior that can single-handedly level a whole city. So it feels weird when it takes several turns for your Space Marine to kill a single Tyranid Prime, and weirder still when your Space Marine gets killed by a random Aeldari infantryman. The same goes for a Monk or Barbarian in D&D or Pathfinder, and of course there are examples for nearly every game.
I very much appreciate the structure of the army list provided in a Warhammer codex or a D&D class description, or an item description, because it helps me learn the intent of the game designers. Whether any given army or character or item actually performs the way it's intended is anybody's guess. But defining intended tactics isn't just game designer augury. It gives you as a player the ability to interpret intention as lore, and then to play a unit according to that lore.
If an army unit is meant to be super fast but nevertheless only has a 6-inch movement, then when it comes time to level up I'm likely to take a bonus to speed over armour or attacks. If a weapon claims to cut through armour, then when I level it up I might take a bonus to armour penetration rather than to straight damage output.
The idea is to get a character or an item to fulfill its own destiny. Of course, in a game (as in life, I guess) whether that happens can be tenuous. Anyone and anything can be cut down in its prime. It only takes a bad roll of the dice. Bus goals go, getting to see a character fully realised is a pretty good reason to keep playing a game.
I'm not so interested in tactics that I view any game just by probability, but I do consider myself a "tactical" player. Or at least, I classify myself as a tactical player, in the sense that I enjoy combat as much as I enjoy roleplay (with no implication that I'm "good" at either!) Maybe a better term would be "mechanical" player, but I'd have to coin it first. What I mean by "tactical" is that I enjoy exploring how the mechanics of a game influence the outcome and story of the game. That, to me, is tactical play, and it negates any desire to "win." What I usually enjoy the most in gaming is getting to see something happen, either by design or as an unexpected side-effect of a series of calculated choices.
In fact, I view a lot of activities in games by how uncommon it is for a player to have witnessed it. When you first take a game out of its box, or you first open the rulebook or codex, you're performing real-world actions that hundreds or thousands of other players have also performed. The Venn diagram is a circle. To call yourself a player of [some game], you must have opened the book to read the rules, taken the board and player tokens out of the box, and so on. 100%
Once you start playing the game, a lot of your actions are also probably pretty common. Lots of people have gone down into the cellar to kill rats in hopes of levelling up. Lots of people have played a Sol Ring on their first turn for the free mana. It's not 100%, but most of the things you're seeing on your tabletop is the same or roughly similar to what all other players are seeing.
The more you play, the more you start experiencing unique events. The Vindicare Assassin pops up in the final round, after 4 rounds of casual smokescreen. Everybody was surprised when the demon with resistance to poison nevertheless died of poison after a cordial but lethal meal with the high-level Monk. Nobody expected a Bear to deal the final blow. Weird stuff happens, and sometimes you're basically the only gaming group to ever witness a specific combination of unlikely events.
This includes developing a character or item or army to its full potential. It's a relatively uncommon thing to achieve. Not all players of a game play it to the bitter end, and even those that do aren't necessarily seeing the same unique combination of benefits and upgrades you've granted your version of the thing. By the end of a Warhammer crusade, I had a Skitarii unit that was fast with lots of bonus armour penetration and a nice invulnerable save for protection, and their commander wielded a rare relic weapon that actually did cut basically anything. What had started out as common out-of-the-box infantry ended up as a unique unit that probably nobody else had ever played.
And best of all, when I read the description of what that army unit was in the lore of the game universe, it finally sounded like a description of the army I was playing on my tabletop.
It takes work to get there. It's a fun job and, for a game you enjoy, it's worth the effort.