Creates a new directory and any missing parent folders at a path relative to ~/src/user for Odoo.sh app development.
Create a directory (including parent directories)
| Name | Required | Description | Default |
|---|---|---|---|
| dirPath | Yes | Directory path relative to ~/src/user |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral burden. It does disclose the useful recursive trait that parent directories are created, but it omits what happens if the directory already exists (error vs. no-op), permission requirements, and the sandbox root implied by the schema.
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?
One short sentence, front-loaded with the verb, and the parenthetical adds real information rather than padding. Nothing is wasted.
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 single-parameter filesystem operation with a fully documented schema, this is nearly sufficient. The only gaps are existing-directory behavior and permission/root assumptions, which is a minor omission for such a simple tool.
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 single parameter's meaning and its 'relative to ~/src/user' base are already fully documented in the schema. The description adds nothing about path syntax or constraints, so the baseline 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?
States a specific verb and resource ('Create a directory') and even distinguishes the recursive scope with '(including parent directories)'. No sibling tool also creates directories, so there is nothing to differentiate against, but the purpose is unambiguous.
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 gives no indication of when to use this versus alternatives such as write_file (which may implicitly create paths) or list_files. There are no stated prerequisites or conditions, so usage must be inferred entirely from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.