Skills tool-design
๐Ÿ“ฆ

tool-design

Content revision r2 Safe โšก Contains scriptsโš™๏ธ External commands๐ŸŒ Network access

Design Reliable Agent Tools

Ambiguous tools cause routing errors, malformed calls, and failed recovery. This skill provides practical patterns for clear schemas, descriptions, responses, and tool catalogs.

Supports: Claude Codex Code(CC)
๐Ÿฅˆ 80 Silver

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "tool-design" from https://skillstore.io/skills/muratcankoylan-tool-design.md and its manifest at https://skillstore.io/api/skills/muratcankoylan-tool-design/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Test it

Using "tool-design". Review a customer lookup tool with an unclear description and generic errors.

Expected outcome:

  • Purpose: Retrieve one customer record by a validated customer identifier.
  • Use when: A request needs account details, status, or identity verification.
  • Recovery: Name the invalid field, expected format, valid example, and retry action.

Using "tool-design". Audit search_orders and find_orders in the same catalog.

Expected outcome:

The tools have overlapping activation scenarios. Merge them or define distinct data sources, filters, return shapes, and selection rules.

Using "tool-design". Assess a catalog with inconsistent customer identifiers.

Expected outcome:

Standardize on customer_id across tool names, parameters, examples, responses, and errors. Add compatibility handling before removing older identifiers.

Security Audit

Safe
v8 โ€ข 8/9/2026 Open versioned report

All 49 static findings are false positives from documentation markup, ordinary prose, or sandboxed command examples. The Python utility performs no network or process execution.

4
Files scanned
1,214
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History โ†’
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/muratcankoylan-tool-design/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/muratcankoylan-tool-design/security.svg)](https://skillstore.io/skills/muratcankoylan-tool-design?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/muratcankoylan-tool-design?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/muratcankoylan-tool-design/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/muratcankoylan-tool-design.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA ยท BibTeX ยท CFF)

APA citation

muratcankoylan. (2026). tool-design security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/muratcankoylan-tool-design/audits/8

BibTeX citation

@techreport{muratcankoylan-muratcankoylan-tool-design-2026, author = {muratcankoylan}, title = {tool-design security audit report (audit version 8)}, institution = {Skillstore}, year = {2026}, number = {8}, url = {https://skillstore.io/skills/muratcankoylan-tool-design/audits/8}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "tool-design security audit report (audit version 8)" version: "unspecified" type: report authors: - name: "muratcankoylan" date-released: "2026-08-09" url: "https://skillstore.io/skills/muratcankoylan-tool-design/audits/8" identifiers: - type: other value: "skillstore:muratcankoylan-tool-design:audit:8" description: "Skillstore immutable audit report identifier"

Compare variants

4 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Highest Skillstore Score
Asmayaseen Recommended

asmayaseen-tool-design

Skillstore Score 81
Evidence Confidence High
Skillstore usage 21
Updated

2026-08-21

muratcankoylan-tool-design

Skillstore Score 80
Evidence Confidence High
Skillstore usage 14
Updated

2026-08-21

chakshugautam-tool-design

Skillstore Score 80
Evidence Confidence High
Skillstore usage 13
Updated

2026-08-21

sickn33-tool-design

Skillstore Score 78
Evidence Confidence High
Skillstore usage 54
Updated

2026-08-21

Skillstore Score

Why this score Evidence Confidence: High
64
Architecture
85
Maintainability
87
Content
70
Community
83
Spec Compliance

What You Can Build

Define a new agent tool

Create a complete description, schema, response shape, and recovery contract before implementation.

Audit an MCP catalog

Identify overlapping purposes, naming collisions, inconsistent parameters, and unclear selection guidance.

Improve failed tool calls

Use observed failures to clarify descriptions, constraints, examples, and retry guidance.

Try These Prompts

Rewrite one tool description
Rewrite this tool description. State what it does, when to use it, accepted inputs, returned data, and recoverable errors: {description}
Design a complete tool contract
Design an agent tool for {workflow}. Include a verb-noun name, typed parameters, defaults, response formats, examples, errors, and retry guidance.
Audit a tool catalog
Audit these tools for overlapping activation scenarios, inconsistent names, schema conflicts, namespace collisions, missing errors, and oversized responses: {catalog}
Evaluate architectural reduction
Compare specialized tools with a sandboxed primitive-tool design for {system}. Assess safety boundaries, routing accuracy, token cost, maintenance, and evaluation criteria.

Best Practices

  • Describe purpose, activation conditions, parameters, returns, and errors as one self-contained contract.
  • Use consistent verb-noun names, parameter terms, namespaces, and response fields across the catalog.
  • Test representative requests and revise descriptions using observed routing and call failures.

Avoid

  • Do not publish vague descriptions that force the agent to guess scope or input formats.
  • Do not create overlapping narrow tools when one workflow tool has a clearer purpose.
  • Do not expose unrestricted command execution without isolation, least privilege, and explicit safety controls.

Frequently Asked Questions

Does this skill create working MCP servers?
No. It guides interface design and provides local description utilities, but it does not implement or run an MCP server.
Can it evaluate an existing tool description?
Yes. The included evaluator checks five textual criteria, but real agent tests remain necessary.
Does the Python utility access the network?
No. It uses standard Python data structures, regular expressions, JSON formatting, and console output.
When should tools be consolidated?
Consolidate tools with overlapping selection scenarios or sequential steps. Keep tools separate when behaviors or independent calling needs differ.
How should MCP tools be named?
Use fully qualified server and tool names. Apply consistent verb-noun conventions and audit provider namespaces for collisions.
Are command-tool examples safe by default?
No. They require a real sandbox, limited data access, restricted privileges, monitoring, and separate security review.

Developer Details

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Ref

02be9409c79ca1183f7844009c14d9df684d0cf9

Maintenance freshness

8/11/2026

Usage

13 downloads ยท 229 views

File structure

๐Ÿ“ references/

๐Ÿ“„ architectural_reduction.md

๐Ÿ“„ best_practices.md

๐Ÿ“ scripts/

๐Ÿ“„ description_generator.py

๐Ÿ“„ SKILL.md

More from muratcankoylan

View all
View all