Did you hear about the concept of category codes in LaTeX?
At the time of tokenizing, i.e., at the time of reading input from the .tex-file and creating tokens and placing the tokens into the token-stream, LaTeX only takes characters of category code 11(letter) for components of names of multiletter control sequences.
Usually the characters a...z and A...Z are of category code 11(letter).
Usually the character @ is of category code 12(other).
Thus usually in .tex-input-files you cannot denote multiletter control sequences whose names contain the character @.
Thus control sequences intended for user-level don't have the character @ in their names.
But there are the control sequences \makeatletter and \makeatother.
\makeatletter gives the character @ the category code 11(letter).
\makeatother gives the character @ the category code 12(other).
This means:
After \makeatletter the character @ will during tokenozation of subsequent .tex-input be treated like any character of category code 11(letter); usually the characters a...z and A...Z are of category code 11(letter).
Thus after \makeatletter you can in subsequent .tex-input denote multiletter control sequences whose names contain the character @.
(By the way: You don't need \makeatletter..\makeatother within .cls-files/documentclass-files and within .sty-files/package-files because LaTeX gives @ the category code 11(letter) automatically during the processing of such files.)
By the \makeatletter...\makeatother-mechanism it is possible to have @ as a character which is only used within the names of control sequences that are not intended to be called by users directly.
Summa summarum:
The character @ in names of control sequences like \iftb@nt@float or \tb@nt@tocentrystyle is just a component of the name of the control sequence in question, like the characters a...z and A...Z (usually) can be components of names of control sequences.
The circumstance that @ is part of the names of these control sequences indicates that the programmer/maintainer of the code intended them not to be used directly by the user.
It also indicates that the definition of the control sequence token in question can change in future releases of the code in question.
Therefore when redefining/modifying code that is maintained by others and that does contain @ in names of control sequences you cannot rely on your redefinitions/modifications to be suitable for future releases of that code, too.
E.g., in the last release of the LaTeX2e-kernel a lot of internal code (containing @ in the names of control sequences) was changed. Such changes can break private modifications of kernel-macros. ;-)
'is just a letter so it is like asking whatadoes\iftb@nt@floatis just a command, it could have been called\iftbzzntzzfloatit's just a name. – David Carlisle Dec 11 '19 at 09:19\DeclareTOCStyleEntry. For more information see the documentation. – esdd Dec 11 '19 at 09:57