Create Nextcloud folder

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

Annotations already indicate it is not read-only, and the description adds that it creates a folder inside the configured root, which clarifies path scoping. However, it does not disclose behaviors like whether intermediate directories are created, error handling if the folder already exists, or permission requirements. Given annotations cover the mutation nature, the description adds minimal extra context.

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 clear sentence with no unnecessary words. It is front-loaded with the verb and resource, and every word adds value.

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 simple one-parameter creation tool, the description covers the core purpose. However, it omits behavioral details like whether it fails if the parent path doesn't exist, if it is recursive, or what it returns. The output schema exists but is not described, and annotations don't clarify side effects. Balanced but with gaps.

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 description must compensate for the single 'path' parameter. It only states 'inside the configured Nextcloud root', implying a relative path, but does not clarify format (slashes), whether recursion is supported, or error conditions. This is minimal added meaning.

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 'Create a folder inside the configured Nextcloud root' clearly states the verb (create) and resource (folder inside a specific location), which distinguishes it from sibling file operations like write_text_file or upload_file_base64.

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 folders but does not explicitly state when to use it versus other tools (e.g., when not to use it, or that it should be preferred over other creation methods). It lacks exclusions or explicit context about alternatives.

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