View available vault skills with their name, description, size, and associated projects, so you can identify relevant standing guidance before starting a session.
List vault skills with name, description, size, and which projects list them. Not session start.
| Name | Required | Description | Default |
|---|---|---|---|
| prefix | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.12.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral burden. 'List' implies a read-only operation and the output fields clarify what is returned. It does not explicitly discuss side effects, filtering, pagination, or ordering, but for a simple list tool this is a modest gap.
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 short sentences front-load the action and core content. 'Not session start' is an economical caveat but terse to the point of being cryptic; still, there is no wasted wording.
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 output schema covers return values and the description states purpose and scope, so basic use is clear. The undocumented prefix parameter and lack of guidance about sibling tools leave gaps for advanced use, but the tool's low complexity keeps the gap moderate.
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?
The schema has one optional 'prefix' parameter with 0% description coverage, and the description never mentions it. An agent cannot tell whether prefix filters by skill name, project, or something else, so the description fails to compensate for the bare 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 uses the specific verb 'List' with the resource 'vault skills' and enumerates returned fields (name, description, size, projects). The 'Not session start' caveat narrows scope but doesn't name a sibling tool, so it stops short of full differentiation.
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 first sentence implies use when a general listing of vault skills is needed, and 'Not session start' provides a narrow exclusion. However, no alternatives are named and no conditions explain when to choose this tool over siblings like get_skill or list_on_demand.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.