Fetch a skill's complete SKILL.md instructions and file manifest for direct injection into agent context or harness. Specify the skill name and optional character limit.
Load a skill's full instructions (SKILL.md body) plus its file manifest, for injection into agent context or harness use.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Skill name from list_skills/search_skills | |
| maxChars | No | Truncate body to this many characters |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the burden of behavioral disclosure. It does clarify that the tool returns the SKILL.md body and file manifest, and the schema documents truncation via maxChars. However, it does not mention error behavior, case sensitivity, what happens when a skill is missing, or whether the manifest is also truncated.
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?
The description is a single, focused sentence that front-loads the core behavior and includes the purpose. There is no redundant or wandering text; every word earns its place.
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?
The tool has only two parameters and no output schema, and the description adequately names the returned content (SKILL.md body and file manifest) and the intended use. It is slightly short on edge-case behavior such as error handling or truncation boundaries, but for a simple retrieval tool this is largely sufficient.
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 description coverage is 100%, so the schema already explains both parameters well. The description adds context about what the skill body is (SKILL.md) and mentions the file manifest, but it does not add substantial new meaning to the parameters beyond what is already in the schema.
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 description states a specific action ('Load') and a specific resource ('a skill's full instructions (SKILL.md body) plus its file manifest'). It also clearly identifies the intended use ('for injection into agent context or harness use'), which distinguishes this tool from siblings like list_skills or search_skills that only return metadata or search results.
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?
The description clearly implies when to use this tool: when the agent needs the full SKILL.md body and file manifest rather than just skill names or search results. It does not explicitly exclude alternatives, but the wording 'full instructions... plus its file manifest' gives a clear context for selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.