tool-design
Designs agent tools: routable descriptions, schemas and response formats, naming, actionable error messages, MCP server design and tool-set consolidation.
- Kind
- Skill
- Works with
- Any agent
- Source
- Agent Skills for Context Engineering @ 9ff0c99108b3
- Path
- skills/tool-design/SKILL.md
- Jobs
- Implementation, Review
- Topics
- Agents & MCP
Credit
- Made by
- muratcankoylan
- Original
- github.com/muratcankoylan/Agent-Skills-for-Context-Engineerin…
- License
- MIT
Listed by Skill Manifest; not made by us.
InstallInstall it from a plugin marketplace.
/plugin install context-engineering@context-engineering-marketplace
Install factsScanned 2 Nov 2026
- Adds
- .claude/skills/tool-design/ (the skill folder)
- 2 file(s) the skill refers to
- Runs scripts
- None found
- Uses the network
- None found
- Needs secrets
- None found
- Source revision
- 9ff0c99108b3
- Licence
- MIT
- Last activity
- 12 Oct 2026
- Review
- Reviewed
Found by a static scan of the stored text; nothing is run. “None found” is not a guarantee, so read what you install before you run it.
- Only the main file is read; other files in the folder are not scanned
# Tool Design for Agents Design every tool as a contract between a deterministic system and a non-deterministic agent. Unlike human-facing APIs, agent-facing tools must make the contract unambiguous through the description alone: agents infer intent from descriptions and generate calls that must match expected formats. Every ambiguity becomes a potential failure mode that no amount of prompt engineering can fix. The unit of work for this skill is a single tool or a tool catalog. Project-shape, pipeline architecture, task-model-fit, and cost-at-the-project-level decisions belong to `project-development`. Deciding whether to introduce sub-agents belongs to `multi-agent-patterns`. This skill owns the interface layer that connects deterministic code to the agent. ## When to Activate Activate this skill when the unit of work is a tool: - Writing a new tool description, schema, or response format. - Debugging cases where the agent picked the wrong tool or generated malformed calls. - Consolidating an overlapping tool catalog (the classic "we have 17 tools, the agent picks wrong half the time" case). - Designing actionable error messages so the agent can self-correct. …