Create folder

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds nothing behavioral beyond that: it never says whether the parent path must exist, whether an existing folder is overwritten or errors out, or whether creation is recursive. Calling it an 'alias' conveys equivalence, not behavior.

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?

It is a single short sentence with no filler, so it is certainly concise, but the brevity comes from omission rather than compression. Nothing is front-loaded because there is no substantive content to order.

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 completely undocumented required parameter, the description supplies neither behavior nor input semantics. An agent cannot verify success conditions, error cases, or the meaning of the path argument from the definition as written.

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 coverage is 0% and the single 'path' parameter is documented nowhere. The description provides no meaning for path — absolute vs relative, whether it names the new folder or its parent, or the expected delimiter/format — so the agent must guess the most consequential input the tool takes.

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 only says it is an alias for create_directory; the actual verb+resource ('create a folder') is inferred from the title and the aliased sibling. It identifies the tool's identity but does not describe what the operation does or how it differs from nextcloud_create_directory, which remains a live sibling in the same toolset.

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?

No guidance on when to use this tool versus nextcloud_create_directory, which it explicitly declares itself an alias of. The agent is left with two indistinguishable tools and no rule for choosing between them, and no prerequisites (parent existence, permissions) are stated.

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