Create Directory

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations indicate it is not read-only (readOnlyHint=false) and not destructive (destructiveHint=false), which is consistent. The description says 'Create', implying mutation. However, it does not disclose behavior if the directory already exists, what happens on error, or the effect of the 'recursive' parameter (default true). More transparency is needed.

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 sentence with no wasted words, but it is overly terse. While concise, it sacrifices clarity and completeness. A slightly longer description structuring the key aspects would be more helpful.

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?

Given the tool has an output schema (not shown) and three parameters, the description is too sparse. It lacks information about error handling, preconditions (e.g., project must exist), return values, or typical usage patterns. The description does not meet the needs of an AI agent selecting between sibling tools.

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 0% coverage for descriptions, yet the tool description does not explain any of the three parameters (projectPath, dir, recursive). It only says 'inside a project', which vaguely hints at projectPath. This is insufficient for an agent to correctly fill in the parameters.

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 states the verb 'Create' and the resource 'directory', and the title reinforces it. It is distinct from sibling file tools (e.g., file.copy, file.delete) because 'mkdir' specifically creates directories, not files or copying. However, it could be more precise about the project context, e.g., 'relative to project root'.

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 is provided on when to use this tool versus alternatives like file.write (for files) or any prerequisites. The description does not mention situations where mkdir is preferable or any caveats (e.g., directory existence).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.