ds_create_folder

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It does not mention what happens on duplicate folder names, permission requirements, whether intermediate directories are created, or error behavior. Only the action and arguments are stated, offering no insight into side effects or edge cases.

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?

The description is brief and well-structured: a one-sentence purpose followed by a compact Args list. Every sentence adds value, with no redundancy or filler, making it easy for an agent to parse quickly.

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?

The description covers the core purpose and parameter semantics but lacks usage context and behavioral details. Given the absence of annotations and output schema, an agent would benefit from additional notes on edge cases or permission requirements, but the description is adequate for a simple create operation.

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?

With 0% schema description coverage, the description effectively compensates by explaining all three parameters. It adds useful context like 'no path prefix' for name, the default '/' for current_dir, and allowed values 'FILE or UDF' for resource_type, which go beyond the bare schema definitions.

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 clearly states 'Create a folder in the resource area' with a specific verb and resource. It distinguishes from sibling tools like ds_online_create_file (file creation) and other ds_create_* tools, leaving no ambiguity about its purpose.

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 provided on when to use this tool versus alternatives, such as when to use ds_online_create_file for files instead. There are no exclusions or prerequisites mentioned, leaving the agent to infer usage solely from the action name.

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