Create Nextcloud folder

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

Annotations already declare readOnlyHint=false, openWorldHint=false, idempotentHint=false and destructiveHint=false. The description adds genuine context beyond that: it relies on a stored account connection (no credential parameters) and stays within a single host. It omits the most operationally relevant behavior, namely what happens if the folder already exists or if parent directories are missing.

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?

Two short sentences with zero filler, and the most important scoping constraint is front-loaded. The second sentence is telegraphic but still earns its place by ruling out shares and cross-host behavior.

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?

An output schema exists, so return values need not be explained, but the definition is thin for a mutation tool: existing-folder handling, parent-directory creation, and path syntax are all unaddressed. It is adequate to start a call and insufficient to predict the result.

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 single 'path' parameter has 0% schema description coverage, so the description must compensate. It partially does by implying the path is relative to the workspace root, but gives no format guidance (leading slash, trailing slash, nested segments, whether intermediate folders are created).

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 one folder') and pins down scope ('only inside the user's connected private Nextcloud workspace root'), which no sibling tool does. An agent can distinguish it from write_text_file or upload_file_base64 without opening the schema.

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 carves out what it will not do ('does not create public shares or contact another host'), which is useful boundary-setting, but never says when to prefer it or how to proceed if a file rather than a folder is needed. Usage is implied rather than stated.

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