Create a new directory at a specified path in VS Code through the Code MCP Server. This tool enables AI agents to generate folders for organizing code files and projects.
Create a new directory
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Path for the new directory |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, and description fails to disclose behavioral traits such as side effects (e.g., what if directory exists), permissions, return value, or error conditions.
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?
Extremely brief (one sentence) but under-specifies essential information. Conciseness at the expense of completeness is not beneficial.
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?
Utterly incomplete for a simple tool. Lacks any context about behavior (e.g., overwrite vs fail), return value, or error handling. Output schema absent.
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 covers 100% of parameters with description 'Path for the new directory'. Description adds no additional meaning beyond schema, so baseline score of 3 applies.
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?
Description states verb+resource (Create a new directory) but is a tautology of the tool name and lacks differentiation from sibling tools like delete_file or move_file. It provides no context on scope or location.
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?
No guidance on when to use this tool versus alternatives. Does not mention prerequisites, when not to use, or related tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.