create_directory

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

With no annotations, description covers idempotency (no failure if exists), automatic intermediate directories, and path constraints. Missing return value/response details, but output schema exists.

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?

Three concise sentences, each adding value. First sentence states action, second explains behavior, third states constraint. No fluff.

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?

Tool is simple with one parameter; description covers core behavior. Could mention return format (e.g., success indicator) but not critical for selection/invocation.

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 describes path, but description adds critical context: absolute path required and automatic creation of intermediate directories, which is not evident from schema alone.

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?

Description clearly states the tool creates a directory, including all necessary intermediates, and equates it to mkdir -p. It distinguishes from sibling file operations like move_file and write_file.

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?

Describes the mkdir -p equivalence and path constraint (must be within allowed directories). Lacks explicit when not to use or alternatives, but purpose is clear.

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