List folder

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description usefully adds that paths are root-relative and that wildcards return matches, but it says nothing about behavior on a missing folder, result ordering, or how max interacts with subfolder listings.

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 front-loaded sentence with the primary scope first and the wildcard variant second; there is no filler and nothing redundant.

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, full parameter documentation, and rich annotations, the description only needs to convey scope and the two calling modes, which it does. The remaining gap is minor: no note on cross-referencing with cloudinary_tree or on wildcard/folder error behavior.

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 every parameter, including defaults and enum values, is documented inline, so the baseline is 3. The description only restates the path/wildcard semantics the schema already explains, adding no new meaning for max, delivery_type, or resource_type.

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 names a specific verb and resource ("List the subfolders and assets of a Cloudinary folder") and adds the dual mode of wildcard matching, so the agent knows exactly what comes back. It does not explicitly contrast itself with the sibling cloudinary_tree, so differentiation is only implicit.

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 examples ("portfolio", "cld*", "shots/*.png") imply the shape of a call, but nothing tells the agent when to pick this over cloudinary_tree or how a folder path differs from a recursive listing. Usage is inferable rather than stated.

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