Resolve an instruction recipe by alias with optional variable interpolation, returning reusable task instructions for AI coding agents.
Resolve an instruction recipe by alias with optional variable interpolation
| Name | Required | Description | Default |
|---|---|---|---|
| vars | No | Key-value map to substitute placeholders like {{key}} | |
| alias | No | Alias keyword to resolve (required) |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
As no annotations are provided, the description adds important functional context by mentioning 'variable interpolation.' This is a specific behavioral trait of how the instruction is resolved, making it more helpful than a generic retrieval description.
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 definition is a single, highly efficient sentence. It front-loads the core functionality (resolve by alias) and includes a key operational detail (variable interpolation) without unnecessary words.
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 retrieval tool, the description is quite complete in terms of inputs. However, since there is no output schema, the description lacks crucial information about the expected return format (e.g., JSON object, raw string, structure).
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?
With schema description coverage at 100%, the baseline for parameter semantics is 3. The description only reinforces the optional nature of 'vars' by linking it to variable interpolation, adding minimal value beyond the existing schema definition.
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 clearly identifies the action ('Resolve') and the mechanism ('by alias'). It is specific but could benefit from explicitly stating that it retrieves a single item, contrasting it with sibling search or list tools.
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?
There is no guidance on when this tool should be used relative to its siblings. It fails to specify, for example, that the alias should be used when the exact instruction name is known, leaving the agent to infer the appropriate lookup method.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.