Create Folder

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

Describes key behaviors: recursive parent creation and idempotent handling of existing folders. No annotations, so description carries burden; missing potential edge cases (e.g., invalid path) but adequate for this tool.

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?

Two sentences, no wasted words, front-loads the main action (create folder path) and key qualifier (mkdir -p).

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?

Simple tool with one parameter; description covers behavior and idempotency. No output schema needed. Complete for intended use.

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 already provides 100% coverage with a clear description and example. The tool description adds no additional information about the path parameter.

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?

Clearly states the tool creates a folder path with mkdir -p behavior, specifically distinguishing from sibling folder operations like delete_folder or move_folder.

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?

Purpose is clear, but no explicit when-to-use or alternatives are given. However, sibling tools are distinct operations, making it unlikely to confuse.

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