get_skillRetrieve the full method for a specific marketing skill, including when to use it, required steps, quality bar, and engine run instructions.
Returns the full method for one skill: when to use it, the steps, the quality bar, and how to run its engine if it has one.
| Name | Required | Description | Default |
|---|---|---|---|
| skill | Yes | Skill slug. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish that this is a safe, idempotent read operation. The description adds useful context about the return payload, including steps, quality bar, and engine-run instructions when present, though it does not mention error behavior or missing-skill handling.
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?
A single well-formed sentence with no filler. The return contents are front-loaded and the description is appropriately sized for a simple lookup tool.
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?
For a one-parameter read-only lookup with rich annotations and no output schema, the description adequately explains what the agent will receive. It could be slightly stronger by mentioning failure behavior for an unknown skill, but the core retrieval contract is clear.
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 'skill' slug parameter is fully documented in the schema. The description adds only the notion of 'one skill' and does not contribute additional format or constraint details beyond 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?
States a specific verb and resource: returns the full method for one skill. It clearly distinguishes itself from search_skills by specifying a single skill lookup and details the payload contents.
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?
Provides no explicit when-to-use guidance or alternatives. The phrase 'when to use it' refers to the skill's own method content, not to when an agent should call get_skill rather than search_skills or run_engine.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.