fetchFetch the complete public catalog record for an exact resource id returned by search, including a canonical citation URL.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Exact resource id returned by search. |
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| url | Yes | ||
| text | Yes | ||
| title | Yes | ||
| metadata | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, so no contradiction. Description adds behavioral context: fetches 'complete public catalog record' and includes citation URL, supplementing annotations.
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?
Single sentence, front-loaded purpose, no wasted words. Efficiently captures all necessary information.
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?
Tool is simple with one parameter and has output schema, so return values need not be described. Description is fully adequate for the tool's purpose.
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 100% coverage, baseline 3. Description adds meaning by emphasizing 'exact resource id returned by search', reinforcing schema description and clarifying usage context.
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?
The verb 'fetch' and resource 'public SuperSkill resource' are clear. It specifies 'complete public catalog record' and 'including a canonical citation URL', adding detail. Differentiates from siblings like resource_detail by requiring an exact id from search.
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?
Explicitly states 'for an exact resource id returned by search', indicating prerequisite use of search tool. Does not list exclusions or alternatives among siblings, but context is clear.
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.
Most tools have distinct purposes, but there is some overlap among search variants (search, search_resources, search_harnesses) and between fetch and resource_detail, which could cause confusion.
Naming mostly follows a verb_noun pattern, but there are inconsistencies such as 'publish_markdown_to_harness' being longer and 'resource_use_instructions' having a different structure.
12 tools is appropriate for a registry server, covering search, fetch, publish, and pull operations without being overwhelming.
The tool set covers core operations (search, fetch, publish, pull) but lacks update and delete functionalities, which are minor gaps for a registry.