Lists approved, pinned, and discovered skills for a specific role or workspace, helping you confirm available capabilities before delegating subagent tasks.
List approved, pinned skills and discovered skills for a specific role or workspace.
| Name | Required | Description | Default |
|---|---|---|---|
| role | No | ||
| workspace_path | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v1.1.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral-disclosure burden. It implies a read-only listing and names skill categories, but it does not state permissions, ordering, pagination, or what happens if neither filter is supplied.
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 front-loaded sentence with no redundant wording. Every part contributes to the scope of the 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?
An output schema exists, so return values need not be explained. However, with no annotations and zero schema description coverage, the description does not provide enough context about usage or parameter behavior for a tool with two optional filtering parameters.
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 0%, and both optional parameters are undocumented in the schema. The description mentions role and workspace_path only indirectly, but it does not explain their meaning, optionality, defaults, or interaction.
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 gives a specific verb ('List') and resource ('skills'), and it further qualifies the skill types as approved, pinned, and discovered. It does not explicitly distinguish this tool from any sibling, but no sibling tool appears to serve the same purpose, so the purpose is still clear.
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 says the tool works for a specific role or workspace, but it gives no explicit guidance on when to call it, when not to call it, or how to choose between role and workspace filters. Usage is only implied by the sentence.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.