docker_mkdir

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

The description discloses that it creates parents ('and parents') and mimics `mkdir -p`, revealing idempotent behavior without requiring annotations. However, it does not mention error handling, permissions, or return values, and with no annotations the description must carry full burden.

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, front-loaded sentence with no redundant information. It earns every word and clearly states the tool's purpose.

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 only two parameters and no output schema, the description adequately conveys the core operation and its semantics. It lacks information about return values or error conditions, but for a directory creation tool this is not critical.

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 schema already fully describes both parameters (`container` and `path`) with clear descriptions, so the baseline is 3. The tool description does not add parameter-specific details beyond the schema.

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 uses a clear action verb 'Create' and specifies the resource 'directory inside a Docker container' with the equivalent of `mkdir -p`. This clearly distinguishes it from sibling tools like docker_read_file or docker_delete.

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?

There is no explicit guidance on when to use this tool versus alternatives such as docker_exec or docker_write_file. The description implies usage through its name and functionality, but does not state exclusions or compare with other tools.

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