Not quite. The current design calls for there to be three different forms of human-readable text, with different availability depending on the type of ZObject:
All ZObjects will have a "label", which will be a set of short textual identifiers, up to one per supported language, shown as the "title" of the page and used in most places aimed at humans using them.
In combination with the 'type' of the ZObject, this is enforced to be unique in a given language (so you can have a 'multiply' function defined that works on two integers and responds with an integer, and another that works on hypercomplex numbers (or matrices or Game of Life implementations or…), but you can't have two that work on the exact same input/output types.
(Note: The current design doesn't have alias support, which Wikidata does.)
ZObjects which are function definitions (ZFunctions), and so may need a lot of documentation and information sharing for people to know how to use it, to expand it, to add new tests, or to add new implementations, will have a fully-featured wikitext description blob/set of blobs, for detailed documentation. These will be the main human starting points and work co-ordination places, so need a lot of the things our communities have come to expect – links, templates, categories, etc..
ZObjects which don't have wikitext description instead have a short, non-wikitext description field, again at a maximum of one per supported language, like how Wikidata works.
