create_directory

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

The description discloses the recursive creation of parent directories and the permit requirement, adding value beyond annotations. However, it does not mention behavior when the directory already exists or error handling, but the key behavioral traits are covered.

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 that immediately states the primary action, then adds the parent-directory nuance and permission requirement with no wasted words.

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 simple tool with one parameter and no output schema, the description covers purpose, permissions, and recursive behavior adequately. It does not specify return values or existence-handling, but these are not critical for a basic directory creation operation.

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 already fully describes the path parameter as 'Absolute or home-relative path for the new directory.' The description adds no additional parameter context beyond this, so the schema carries the semantic load, matching the baseline score.

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 specifies 'Create a new directory' with the additional detail of creating missing parent directories, clearly distinguishing it from sibling file tools like list_directory or delete_file. The verb+resource is explicit and 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 clearly indicates this tool is for creating directories and notes the prerequisite allow_file_write permission, providing clear context. It doesn't explicitly state when not to use it or name alternatives, but for a directory creation tool this is sufficient context given sibling tool names.

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