search_skillsFull-text (BM25) search over the skills directory. Returns ranked matches with slug, title, description, categories and price.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| query | Yes | Search terms, e.g. "cold email sequence". |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Describes the search algorithm (BM25) and ranked results, but no annotations exist. Lacks disclosure of read-only nature, authentication needs, or rate limits. Adequate but not fully transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences only, direct, no filler. Efficiently communicates core functionality.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Covers search method, ranking, and output fields. With no output schema, description provides necessary output details. Minor omission: no mention of pagination or default limit, though schema defines limit.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema has 50% coverage (only query has description with example). Tool description adds no additional parameter context beyond schema. Limit parameter remains undocumented in both.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states it performs full-text (BM25) search over the skills directory, with explicit output fields (slug, title, description, categories, price). Distinguishes from sibling tools like list_skills (lists all) and recommend_skill (recommends based on criteria).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus siblings (e.g., list_skills, recommend_skill). No preconditions or exclusions mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool serves a distinct purpose: retrieving sets, skills, categories, sets list, skill list, recommendation, and search. No overlapping functionality.
All tools use consistent snake_case with verb_noun pattern (e.g., get_set, list_categories, search_skills). No mixing of styles.
Seven tools is well-scoped for a skills directory, covering browsing, search, recommendation, and detailed retrieval without overburdening the agent.
Covers core operations: listing categories, skills, sets; searching; recommending; retrieving details. Minor gap: no direct category detail tool, but list_categories provides counts.