I am going to assign the comment directly to the relevant parameter, like "resistance".
A word of caution, having gone done this road myself--it's tempting to go crazy with your database structure and throw in columns for all kinds of different parameters, so that you have a ton of useful parametric information right in your part library, but this is ultimately a waste of time in my experience. You either have a ridiculous number of columns in one database table, or you have to have separate tables with different schemes for each class of part, and both quickly get unwieldy and difficult to maintain.
Instead, just put in the primary value for the part, a human-readable description that captures key specs, and a link to the datasheet. For most jelly bean parts, all you need is that short description when picking something out from your library (and the description is especially helpful in BOMs, etc, because it immediately tells the reader what sort of thing it is without having to decipher a PN). For more complicated parts (ICs, even transistors and diodes in some cases) you will *never* be able to capture all of the factors that go into determining whether a particular part is fit for your purpose in a set of database fields anyway, and that's where the datasheet link comes in. If you follow Altium's field naming for it, it will even be available via right click in the schematic editor.
For situations where you want a bit more info to appear on the schematic, you can add a couple of "special" fields to the database, and as long as your consistent in how you use them ("Special 1" is always tempco for resistors and dielectric for capacitors, etc) it's easy to create alternate schematic symbols that show those parameters automatically. That way your basic pullup resistors that don't really matter can just show a resistance, but for your analog section you can clearly specify where the special high precision $5/ea ones go.