create_directory

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

No safety annotations like readOnlyHint or destructiveHint are provided, so the description carries the burden of behavioral disclosure. It only mentions a prerequisite (registered writable vault) and does not disclose side effects, failure conditions, or permission requirements for the create operation.

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 a specific verb and object. It contains no redundant words and every word contributes to the meaning.

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?

This is a mutating tool with no output schema, no parameter descriptions, and minimal annotations. The description leaves critical gaps about how the directory path should be specified, what happens on conflicts, and what the vault registration/writability requirements actually entail.

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 input schema has no descriptions for vault or directory (0% coverage), and the description only repeats the concepts of 'vault' and 'directory' without explaining the expected path format, relative vs absolute, or any constraints. The description fails to compensate for the lack of schema documentation.

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), the resource (directory), and the scope (inside a registered writable vault). This distinguishes it from sibling tools like create_note and create_vault, making the purpose specific and 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?

The description implies usage for creating directories within an existing registered vault, but it does not explicitly state when to use this tool over alternatives or provide exclusions. The prerequisite 'registered writable vault' gives some context but no direct comparison to siblings.

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