devtu-optimize-descriptions

Optimize ToolUniverse JSON tool descriptions with prerequisites and filter syntax.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/Centaurioun/osteogenesis_imperfecta --skill devtu-optimize-descriptions-centaurioun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devtu-optimize-descriptions
Source: https://github.com/Centaurioun/osteogenesis_imperfecta/tree/main/.agents/skills/devtu-optimize-descriptions
Command: npx skills add https://github.com/Centaurioun/osteogenesis_imperfecta --skill devtu-optimize-descriptions-centaurioun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many ToolUniverse JSON tool descriptions are ambiguous, inconsistent, or missing critical information such as prerequisites, mutually exclusive inputs, and realistic examples, which leads to user errors and longer onboarding time. This Skill provides structured guidance and concrete fixes to transform terse or vague descriptions into actionable, testable documentation that new users can follow on first try.

Core Features & Use Cases

  • Prerequisite injection: Ensure each tool lists required packages, API keys, or account steps so users can prepare before running tools.
  • Mutually exclusive input clarity: Mark mutually exclusive inputs as "Required: Provide ONE input type" and label options as Option 1/2/3 to prevent incorrect combinations.
  • Filter & parameter guidance: Expand filter syntax with operators, common fields, and examples and explain parameter trade-offs with recommended defaults.
  • Use Case: Audit a ToolUniverse JSON bundle before release to add prerequisites, expand abbreviations, improve filter examples, and validate that parameter choices are clearly explained.

Quick Start

Use the devtu-optimize-descriptions skill to review a tool's JSON description and update it to include prerequisites, expanded abbreviations, clear required inputs, filter syntax examples, and recommended defaults.

Frequently Asked Questions about devtu-optimize-descriptions

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

FAQPage Schema
How do I optimize tool descriptions in JSON configurations?

Optimizing tool descriptions in JSON configurations involves adding prerequisites, expanding abbreviations, clarifying mutually exclusive inputs, and providing filter syntax examples. This ensures the documentation is clear, consistent, and actionable for new users.

What is the best way to document mutually exclusive inputs in tool JSON?

The best way to document mutually exclusive inputs in tool JSON is to label them as "Required: Provide ONE input type" and mark options as Option 1/2/3. This clearly prevents incorrect parameter combinations and user errors.

How do I add filter syntax and parameter guidance to JSON documentation?

To add filter syntax and parameter guidance to JSON documentation, expand the syntax with operators, common fields, and examples. You should also explain parameter trade-offs and include recommended defaults for better user onboarding.

Why do JSON tool descriptions need prerequisites and expanded abbreviations?

JSON tool descriptions need prerequisites and expanded abbreviations to prevent user errors and reduce onboarding time. Listing required packages and API keys ensures users can properly prepare their environment before running tools.

Can I audit a ToolUniverse JSON bundle to validate parameter descriptions?

You can audit a ToolUniverse JSON bundle before release to validate parameter descriptions. This process adds prerequisites, expands abbreviations, improves filter examples, and ensures parameter choices and trade-offs are clearly explained for users.