skills.rest
AvaTar-ArTs
AvaTar-ArTsCOMMUNITY
Explore all skills by this author →
GitHub

devtu-optimize-descriptions

Review and improve tool descriptions in ToolUniverse JSON configuration files.

Updated Jul 10, 2026
Search Tags:#documentation#json#usability#review#api documentation#tooluniverse#tool descriptions
One-click install
npx skills add https://github.com/AvaTar-ArTs/.Agent-skills --skill devtu-optimize-descriptions-avatar-arts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: devtu-optimize-descriptions
Source: https://github.com/AvaTar-ArTs/.Agent-skills/tree/main/skills/devtu-optimize-descriptions
Command: npx skills add https://github.com/AvaTar-ArTs/.Agent-skills --skill devtu-optimize-descriptions-avatar-arts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Tool descriptions in ToolUniverse JSON configs are often unclear about required inputs, prerequisites, abbreviations, and parameter trade-offs, causing user errors and failed first attempts. ## Core Features & Use Cases - Critical Fixes: Clarify mutually exclusive required inputs, add prerequisites (packages, API keys, accounts), and expand abbreviations on first use. - Parameter Guidance: Enhance filter descriptions with operators, field lists, and examples; explain option trade-offs and recommend defaults. - Quality Validation: Apply checklists, before/after metrics, and JSON syntax validation commands to verify improvements. - Use Case: When adding a new tool to ToolUniverse, run this review to ensure users can understand and correctly call the tool on their first try without external documentation. ## Quick Start Review the tool descriptions in my ToolUniverse JSON config and improve them for clarity and usability.

Frequently Asked Questions about devtu-optimize-descriptions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I improve tool descriptions in JSON config files?▼

Review each description for clear purpose, stated prerequisites, expanded abbreviations, and parameter guidance with examples. Mark mutually exclusive inputs with bold labels like "Required: Provide ONE input type" and number the options.

What makes a good API tool description?▼

A good description states the action and purpose, lists prerequisites, describes data scale, clarifies required inputs, notes limitations, and ends with 3-5 concrete use cases. Aim for 30-60 words.

How should I document filter parameters in tool configs?▼

Describe the syntax format, list available operators (==, !=, in, <, >), name 5-10 common filterable fields, and provide 2-3 diverse examples showing realistic queries.

How do I validate JSON tool configuration files?▼

Run python3 -m json.tool on each file to check syntax validity. You can loop over all *_tools.json files in the data directory and report which ones pass or fail validation.

When should abbreviations be expanded in documentation?▼

Expand abbreviations on first use using the format "Abbreviation (Full Name)", such as H5AD (HDF5-based AnnData) or TSS (Transcription Start Site). This helps users unfamiliar with domain terminology.

Related Skills

Explore More Software Engineering Skills→
CentauriounCentaurioun

devtu-optimize-descriptions

Optimize ToolUniverse JSON tool descriptions with prerequisites and filter syntax.

Community
Intermediate
CentauriounCentaurioun

create-tooluniverse-skill

Generate tested ToolUniverse skills with templates and fallback strategies.

Community
Advanced
kis9akis9a

doc-generator

Generate and update Go documentation from source code.

Community
Advanced
mgoodman60mgoodman60

docs

Generate structured documentation from JavaScript/TypeScript codebases using inline comments and type definitions.

Community
Intermediate