---
id: "contrarian-description-over-instructions"
type: "contrarian-insight"
source_timestamps: ["00:01:46"]
tags: ["prompt-engineering", "agent-design", "tool-routing"]
related: ["claim-description-importance", "framework-skill-anatomy", "quote-description-matters"]
challenges: "The assumption that the actual prompt instructions are the most vital part of an AI automation tool."
sources: ["alex"]
sourceVaultSlug: "claude-skills-content-automation-2026May14"
originDay: 1
---
# Routing Logic Trumps Execution Logic

## What this challenges

The default builder instinct: *the prompt body is the brain of the tool, so spend all your time there.*

## The contrarian reframe

For Claude Skills (and most agentic tool architectures), the **trigger description** is more leveraged than the instruction body. If routing fails, execution never happens. A dormant Skill with brilliant instructions is worth zero. A firing Skill with mediocre instructions still produces output.

Spend disproportionate effort on:

- Phrasing the description in the **user's natural language**.
- Specifying the **trigger condition** precisely.
- Including the **vocabulary** users actually use (synonyms, casual phrasings).

See [[claim-description-importance]], [[quote-description-matters]], and the routing layer of [[framework-skill-anatomy]].

## Honest counter-position (from enrichment)

This is opinionated emphasis on a real failure mode, not an absolute hierarchy. Modern tool routers consider tool names, parameter schemas, examples, and sometimes historical usage in addition to descriptions. **Both layers are critical.** A more rigorous framing: *routing is a frequently overlooked failure point that builders systematically underinvest in.* Don't let "descriptions matter more" become permission to ship sloppy instructions.