Move or rename

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

Annotations already declare destructiveHint, idempotentHint=false, and openWorldHint, so the safety profile is covered. The description still adds real value by disclosing the confirmation gate and the URL-preservation behavior in dynamic folder mode, which are not visible from annotations alone.

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?

Three sentences, no waste, with the core action front-loaded and the confirmation mechanics trailing as supporting detail. Every sentence carries distinct information.

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, rich annotations, and full schema coverage, the description only needs to explain the non-obvious workflow, which it does via the confirm_token gate. Minor gap: it does not mention permission requirements or what happens to the existing asset when overwrite replaces it.

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 100%, so every parameter including dry_run, overwrite, and confirm_token is already documented in the schema. The description's 'keeps its URL unless change_public_id is set' largely restates the schema's own wording, so it adds little beyond the structured fields – baseline 3.

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 ('Move or rename an asset, or move a folder') and names the dynamic folder mode qualifier. It does not explicitly distinguish itself from the sibling cloudinary_rename_folder, which overlaps on folder operations, so an agent may still hesitate between the two.

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?

Gives useful context about the two-step confirmation flow ('first call returns needs_confirmation... confirm_token'), which tells the agent how the call sequence works. However, it never says when to prefer this over cloudinary_rename_folder or when to use dry_run instead of a real call, and offers no exclusions.

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