devtu-optimize-descriptions

Optimize tool descriptions in ToolUniverse JSON configs for clarity and usability. Reviews descriptions for missing prerequisites, unexpanded abbreviations, unclear parameters, and missing usage guidance. Use when reviewing tool descriptions, improving API documentation, or when user asks to check if tools are easy to understand.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/devtu-optimize-descriptions/SKILL.md

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable and well-sequenced content with concrete examples and validation, undermined by redundancy and a monolithic structure that bundles material which would be clearer split across reference files. Tightening duplication and externalizing the tool-type pattern catalogue would lift the weaker dimensions.

Suggestions

Consolidate the two checklists into one and trim the final before/after example so it does not duplicate sections 1, 5, and 6, removing the redundant Summary re-listing.

Move the 'Common Patterns by Tool Type' templates and the full before/after example into references/ files (e.g. tool-type-patterns.md), keeping SKILL.md as a lean overview that links out.

Add an explicit validation feedback loop — e.g. after running json.tool, 'if invalid, fix the JSON error and re-run until ✓ Valid' — to make the verification step a true retry loop.

Dimension	Reasoning	Score
Conciseness	Mostly useful content, but noticeably redundant: two separate checklists, before/after examples repeated verbatim in the final example, and a Summary that re-lists all nine improvements already detailed above.	3 / 5
Actionability	Concrete JSON before/after pairs, copy-paste bash validation commands, specific formatting rules ('Required: Provide ONE input type', 'Abbreviation (Full Name)'), and per-tool-type templates give fully actionable guidance.	5 / 5
Workflow Clarity	A clear priority-ordered sequence (Critical → High → Medium) with a dedicated Validation Commands section and checklists; validation is present so the batch-operation cap does not apply, but an explicit validate → fix → retry loop is missing.	4 / 5
Progressive Disclosure	Headers and priority groupings give good in-file structure, but the skill is monolithic (~347 lines, no references/scripts/assets bundle) with tool-type patterns and the full before/after example inlined where separate reference files would aid navigation.	3 / 5
	Total	15 / 20 Passed

Description

88%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it names a specific niche, lists concrete review actions, and provides explicit 'Use when' triggers. The main weakness is the somewhat broad 'API documentation' trigger and a lack of synonyms/extensions that would maximize natural-term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete review actions — 'missing prerequisites, unexpanded abbreviations, unclear parameters, and missing usage guidance' — anchored to a named domain (ToolUniverse JSON configs), matching the comprehensive-coverage anchor.	5 / 5
Completeness	Clearly states what it does (optimize/review tool descriptions) and an explicit 'Use when ...' clause with three concrete trigger conditions, matching the both-what-and-when anchor.	5 / 5
Trigger Term Quality	'reviewing tool descriptions', 'improving API documentation', and 'user asks to check if tools are easy to understand' are natural trigger phrases, but synonyms and file extensions are largely absent.	4 / 5
Distinctiveness Conflict Risk	The ToolUniverse JSON-config niche is distinct, but the 'improving API documentation' trigger is broad enough to create minor overlap with general documentation skills.	4 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: mims-harvard/ToolUniverse
Path: skills/devtu-optimize-descriptions/SKILL.md
Commit: 1b02920

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.