create_directory

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

With no annotations provided, the description must fully disclose behavior. It states 'recursively' which implies parent directory creation, but fails to specify key behaviors: what happens if the directory already exists? Does it fail or succeed silently? No error handling or permission requirements are mentioned.

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?

Single short sentence that is front-loaded with the core action. No extraneous words. Every word is meaningful. Appropriate for a simple tool.

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?

Given the lack of annotations and output schema, the description is incomplete. It omits critical details: return value (does it return success/error?), idempotency behavior, and concurrency implications. A directory creation tool with one parameter and no output schema needs at minimal to state what happens on existing paths.

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 coverage is 0% (parameter has no description in schema). The tool description does not elaborate on the 'targetPath' parameter—no format expectation (absolute/relative), no constraints, no example. The agent gets no additional meaning beyond the schema's basic type.

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 'Creates a directory recursively' clearly states the action (create) and resource (directory). The 'recursively' qualifier distinguishes it from a non-recursive creation, and sibling tool names like list_directory and write_file imply this tool is for directory creation, making purpose unambiguous.

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 or not use this tool. No mention of alternatives (e.g., for file creation use write_file). The agent is left to infer usage context from the tool name alone.

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