cloudinary_mkdirCreates a folder path in Cloudinary, automatically creating any missing parent folders so nested directories can be set up in one call.
Create a folder (missing parent folders are created too).
| Name | Required | Description | Default |
|---|---|---|---|
| folder | Yes | Folder path from the root |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=false, idempotentHint=true, openWorldHint=true, and destructiveHint=false. The description adds one genuinely useful side-effect disclosure: missing parent folders are created too. Beyond that it adds no context on permissions, path format, or behavior when the folder already exists (partly covered by idempotentHint).
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 sentence with the key side-effect front-loaded in parentheses. No wasted text.
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?
With an output schema present and rich annotations, the description supplies what's needed to call the tool correctly. Minor gaps remain (path format, no-op behavior on existing folders) but they are largely covered by the idempotentHint annotation.
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 100% and the single parameter documents itself as "Folder path from the root". The description adds no syntax, separator, or format detail beyond the schema, so the baseline 3 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 folder") with a parenthetical scope note. It is unambiguous and no sibling (rename_folder, move, upload) overlaps with plain folder creation, though it doesn't explicitly say so.
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?
Usage is implied by the verb – you call it when you need a folder to exist – but there is no explicit when/when-not guidance or reference to alternatives such as cloudinary_rename_folder or cloudinary_move for other path operations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.