Create Folder

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing about this write operation: whether it is recursive, whether it errors or silently succeeds when the folder already exists (idempotency), what permissions are needed, or whether the change is reversible. For a mutation tool with zero annotation coverage this is a substantial gap.

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?

A single short sentence that is front-loaded with the action and contains no filler. It is efficient, though its brevity borders on under-specification rather than tightness.

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?

The tool is simple (one required string parameter, no nesting, no output schema), so the description covers the core intent adequately. However, with no annotations and no output schema, the missing idempotency/error/return-path information leaves meaningful behavioral territory unexplained for a write operation.

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 100% — the single 'folderPath' parameter is documented in the schema as 'The path for the new folder'. The description adds no meaning beyond that (no note on absolute vs. relative paths, leading slashes, or path separators), so the baseline 3 for a fully described schema applies.

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?

States a specific verb and resource ('Create a new folder') plus the scope ('in the vault'), which is enough to distinguish it from the note-centric siblings like obsidian-create-note or obsidian-list-files. It stops short of naming a sibling or spelling out the contrast, so it is clear but not fully differentiated within the description itself.

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 guidance on when to use this versus the note tools, and no prerequisites such as whether parent folders must already exist or whether the vault must be unlocked/accessible. The agent must infer all usage conditions from the tool name.

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