create_directory

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

With no annotations provided, the description must fully disclose behavioral details. It only states that a directory is created, but does not say whether the path is relative to the project root, whether intermediate directories are created, or what happens if the directory already exists. This lack of behavior disclosure leaves important questions unanswered.

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, clear sentence with no wasted words. It is appropriately concise for a simple tool, though it could have been slightly longer to include usage guidance without losing conciseness.

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 tool is relatively simple, and the schema covers the only parameter. However, the description lacks contextual information such as the relative path requirement, potential failure modes, or relationship to similar tools. This makes it adequate but not fully complete for an agent to use effectively.

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 input schema describes the single 'path' parameter with 'Directory path to create (relative to project root)', so schema coverage is 100%. The description adds no additional meaning about the parameter. The baseline of 3 is appropriate because the schema already provides full parameter semantics.

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 tool's function: 'Create a directory in project.' This is a specific verb and resource, and it is distinct from other create_* tools. However, it does not distinguish itself from the sibling tool 'editor_create_folder', which seems to have a similar purpose.

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 guidance on when to use this tool versus alternatives such as 'editor_create_folder' or 'move_file'. There is no mention of prerequisites, limitations, or preferred contexts. The lack of any usage direction makes this a minimal, unhelpful description for tool selection.

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