Optimize tool descriptions in ToolUniverse JSON configs for clarity and usability. Reviews descriptions for missing prerequisites, unexpanded abbreviations, unclear parameters, and missing usage guidance.
SkillScore36Maintained
Automatic
◆Doc Ops pack
Last verified 7/28/2026
What it changes
Passed 8 of 22 test cases with the skill, and 0 of 22 without it.
Without skill0%
With skill36%
8 fixed0 passed either way14 still failing0 broke
Pass-rate lift
+36 pp
Tokens
+173%
Agent turns
0%
Response time
-16%
Model gemini-3.6-flashMeasured 7/28/2026v18 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
What's inside
The instructions your model reads when the skill loads.
SKILL.md342 linessingle file
ToolUniverse Tool Description Optimization
Optimize tool descriptions in ToolUniverse JSON configuration files to ensure they are clear, complete, and user-friendly.
When to Apply This Skill
Use when:
Reviewing newly created tool descriptions
User asks "are these tools easy to understand?"
Improving existing tool documentation
Adding new tools to ToolUniverse
User mentions tool usability, clarity, or documentation
Quick Optimization Checklist
Tool Description Review:
- [ ] Prerequisites stated (packages, API keys, accounts)
- [ ] Critical abbreviations expanded on first use
- [ ] Required vs optional parameters clear
- [ ] Mutually exclusive options numbered/labeled
- [ ] Parameter guidance includes trade-offs
- [ ] Filter syntax shows available fields
- [ ] File size warnings where relevant
- [ ] Examples show realistic usage
Critical Improvements (Fix Immediately)
1. Clarify Required Input Requirements
Problem: Users don't know if they need ONE input or ALL inputs.
Fix: Use "Required: Provide ONE input type" for mutually exclusive options.
// Before
"description": "Process BED regions, motifs, or gene lists..."
// After