创建目录

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

The readOnlyHint=false annotation already signals mutation, and the description adds meaningful behavior beyond that: recursive creation and workspace scoping. It does not disclose failure behavior or what happens if the directory already exists, but the core side effect is clearly stated.

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 with no redundant wording. The essential behavior (recursive creation) is front-loaded and every word earns its place.

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 one-parameter tool, the description covers the main purpose and the recursive behavior. However, there is no output schema, no parameter detail, and no mention of failure semantics or whether the directory must be inside the workspace. It is minimally viable but leaves some practical gaps.

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 description coverage is 0%, so the description must compensate. It only implies that 'path' refers to a workspace directory, without explaining path format, relative vs absolute, or whether it must be a new path. This is minimal added meaning beyond the schema's type and property name.

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 action ('创建' / create) and the resource ('工作区目录' / workspace directory), and adds the key recursive behavior. This distinguishes it from sibling file operations like write_file, delete_path, and move_path.

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?

The usage context is implied: use this tool when you need to create a workspace directory, including parent directories. However, it does not explicitly state when not to use it, mention alternatives, or address edge cases like existing directories.

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