Name objects through function, limits and ownership
Give equipment a distinct role without relying on increasingly grand claims of rarity or power.
An inventory full of legends stops distinguishing anything
If every other blade is eternal and every amulet claims ancient power, the adjectives say little about an individual discovery. Ask instead what distinguishes the object in use and in history. The answer can be modest: it was repaired, changed owner or was built for a particular task. Such differences often support a memorable name more effectively than another claim of greatness.
Separate the functional type, the source or maker and the personal name. An ordinary tool does not need all three. Deliberately leaving some objects with plain labels makes the genuinely important ones stand out later. The interface should still explain function even when the story gives an item a poetic identity.
Rarity is a reason, not a complete property
An object may be rare because its material is difficult to obtain, because few people know its construction or because its original use is no longer common. Those causes produce different stories. Choose one and show it through a visible property. Repeating the same valuable-sounding prefix across a tier of equipment does not communicate these differences.
Keep mechanical information distinct from the personal name. A famous object can be damaged; an unremarkable-looking tool can have an unusual capability. If the description makes this clear, the contrast between reputation and actual condition becomes interesting rather than misleading.
Compare the work each candidate demands
An oath-related name asks who promised what to whom. A place-related name asks which maker or region matters. An event-related name asks what happened and whose memory survives. None of these approaches is universally better. They require different supporting material, and the most impressive candidate may be unsuitable if the project has no room for that story.
Test each form against the smallest actual use. The inventory entry may need a neutral type alongside the proper name. A letter from an earlier owner can use a private form, provided the connection is introduced. Record that relationship so the audience does not mistake two names for two objects.
Give unusual abilities a visible limit
A lantern that reveals hidden writing needs a different promise from a light that detects every lie. A compass pointing towards a lost possession does not automatically know a safe route home. Describe what the object cannot do before naming it. That boundary creates choices and prevents a poetic label from implying an ability the rules never support.
The limit should be observable early enough for later decisions to feel fair. Fuel can run out, a signal can depend on a condition or a stored memory can be incomplete. Do not invent a convenient exception only when the plot would otherwise become easy. The name may hint at the limit, but the usable rule belongs in a clear description too.
Exercise: two owners and a transfer
Plan an initial owner, a later owner and the event that transfers the object. One calls it by its maker’s label; the other names it after an experience. A repair, worn emblem or mismatched case can preserve the earlier history without magical speech or an all-knowing narrator.
Document the principal name, functional type and important variants together. If a story event deliberately changes the visible name, make the transition understandable in the interface. The new form gains weight when it records an actual choice rather than simply announcing an upgrade.