create_directory

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

With no annotations, the description must disclose all behavioral traits. It only mentions error in read-only mode. Missing: behavior if directory exists, return value, permission requirements, or side effects beyond directory creation.

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 short sentence, which is compact. However, it sacrifices necessary detail for brevity, making it under-specified. It is not as concise as it could be if it included key behavioral points.

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 1-parameter tool with no output schema and no annotations, the description is incomplete. It covers creation and parent directory creation but omits critical context like handling of existing directories, success/error responses, and potential side effects.

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 sole parameter 'path' has no description in the schema (0% coverage). The tool description adds no additional meaning, such as format, relative vs absolute, or allowed characters, leaving the agent with only the raw name 'path'.

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 explicitly states the action ('create a directory') and resource ('directory'), and adds that it includes parent directories. This clearly distinguishes it from sibling file operations like append, move_file, 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?

No guidance on when to use this tool versus alternatives (e.g., write_file for file creation). The only usage hint is 'Returns error in read-only mode,' which is a condition, not a comparison with other tools.

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