---
id: "claim-description-importance"
type: "claim"
source_timestamps: ["00:01:46"]
tags: ["prompt-engineering", "system-design", "tool-routing"]
related: ["framework-skill-anatomy", "contrarian-description-over-instructions", "quote-description-matters"]
confidence: "high"
testable: true
speakers: ["Alex (Grow with Alex)"]
---
# Skill Descriptions Matter More Than Instructions

## Claim

When building a [[concept-claude-skills]] file, the **trigger description in the frontmatter matters more than the instruction body itself.**

See the supporting [[quote-description-matters]] and the contrarian framing in [[contrarian-description-over-instructions]].

## Mechanism

Claude's agentic architecture scans the *descriptions* of all available Skills in scope and uses them to decide which Skill to fire for the user's current request. The instruction body only runs *if* the description matches. So:

- **Bad description, brilliant instructions** → Skill stays dormant, never fires.
- **Good description, mediocre instructions** → Skill fires every time, produces OK output.

This routing-vs-execution framing maps directly onto the three-part [[framework-skill-anatomy]].

## How to write a good description

- Use the natural-language phrasing the user is likely to type.
- Be specific about the *trigger condition* ("when the user asks for video hooks").
- Include relevant keywords (hook, headline, opener, cold open).
- Avoid vague verbs like "helps with" or "handles."

## Confidence & caveats (from enrichment)

**Confidence: high on the underlying mechanism; medium on the strong framing.**

Tool-routing research across OpenAI function calling, Google tool use, and Anthropic tool use confirms that **metadata and descriptions strongly affect tool selection**. The literal claim that descriptions "matter *more than*" instructions is an opinionated emphasis — a more balanced framing is that **routing is a common, often-overlooked failure point** and both layers (routing metadata + execution logic) are critical. Don't under-invest in instructions just because descriptions are upstream.