Create directory

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), lowering the bar. The "MKCOL" reference adds a genuine technical signal — WebDAV collection creation, which implies parents are not auto-created and an existing collection yields an error — but the description never states that behavior explicitly, nor what happens on conflict.

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?

One short, front-loaded sentence with no filler. It is efficient, though its brevity borders on under-specification rather than tight scoping.

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 mutation tool with no output schema and a fully undocumented required parameter, the definition should cover path format and existing-directory/conflict behavior. Neither is addressed, so an agent cannot reliably construct a correct call.

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 single `path` parameter is entirely undocumented in both schema and description. The description does not say whether the path is absolute or relative to the user root, whether a leading slash or trailing slash is expected, or which parent it is created under.

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+resource ("Create a directory") and adds the WebDAV method (MKCOL), so the operation is unambiguous. It does not distinguish itself from the sibling nextcloud_create_folder or nextcloud_create_resource-style tools, leaving the agent to infer the difference.

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 nextcloud_create_folder, which appears to overlap directly, nor on prerequisites (parent existence, permissions). The agent must guess which creation tool to pick.

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