This walks through ToolUniverse JSON configs and flags descriptions that will confuse users. It checks for missing prerequisites, unexpanded abbreviations like H5AD or TSS, unclear required versus optional parameters, and mutually exclusive options that need numbering. The checklist is thorough, maybe overly so, but it catches real problems like filter parameters that don't explain available fields or parameters that don't explain trade-offs. Run this when you're adding new tools or when someone asks if their API documentation makes sense. The examples are bioinformatics-heavy, which shows where this came from, but the patterns apply to any tool configuration that needs to be self-explanatory.
npx skills add https://github.com/mims-harvard/tooluniverse --skill devtu-optimize-descriptions