Create an asset folder

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

The annotations provide only idempotentHint=false, so the description carries the burden of explaining effects. It does not disclose what happens on duplicate slugs, whether parent_folder_id must exist, or what the response contains, leaving important behavioral traits ambiguous.

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?

Two short sentences with no filler, and the core purpose is front-loaded. The second sentence adds relevant context about the slug, earning its place.

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, the description should explain return value and edge cases (e.g., duplicate slug, invalid parent_id). It contains neither, so an agent cannot fully predict the outcome of the call.

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?

All three parameters are fully documented in the schema (100% coverage), so the description only needs to add extra meaning. It adds a useful clarification that the slug appears in the URL of every file inside the folder, which goes beyond the schema's 'URL segment' description.

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 states a clear verb ('creates') and a specific resource ('a folder in the asset store'), which distinguishes it from sibling operations like list_asset_folders, upload_asset, or delete_asset. However, it does not explicitly name a sibling or contrast path, so it stops short of the best-practice standard.

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 is given on when to choose this tool over alternatives, such as list_asset_folders (reading) or upload_asset (adding files). The only usage hint is that the slug affects all file URLs, which is more of a naming tip than a selection criterion.

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