Avoid unexplained jargon or abbreviations in descriptions
description
A tool description is read by the model with no additional context beyond what is written -- internal codenames, uncommon abbreviations, or jargon specific to one team should be spelled out or avoided, the same way a new team member would need it explained.
good example
"CSL (Citation Style Language) JSON" spelled out on first use.
bad example
"Returns CSL data." with no expansion anywhere in the tool description or schema.
source note
General clarity best practice, consistent with this repo's own style-citations skill spelling out CSL on first use.
provenance
created 2026-07-02 08:28:30 · JSON