create_directory

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

Annotations already indicate non-destructive and non-read-only behavior. The description adds valuable detail about nested directory creation and automatic path normalization, which goes beyond annotations. No contradiction noted.

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 verbose with bullet points and repeated emphasis on absolute paths, but it remains organized and front-loaded. Some sentences could be condensed without losing clarity.

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 path usage thoroughly and mentions constraints like allowed directories. No significant gaps for typical usage.

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 has no description for the single 'path' parameter (0% coverage). The description compensates extensively by explaining path normalization, absolute vs relative recommendations, and tilde path caveats, adding significant meaning.

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 creates a directory or ensures it exists, with the ability to create nested directories. This is a specific verb+resource combination that distinctly differs from sibling tools like write_file or read_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?

Provides explicit guidance on when to use absolute paths, handling of relative and tilde paths, and mentions it only works within allowed directories. While alternatives aren't compared, the context is clear for a directory creation tool.

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