Create a folder

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

Beyond the annotations, the description discloses meaningful behavior: missing parent folders are created, existing folders are left as-is, and write permission is required. The 'existing folder is left as it is' detail aligns with idempotentHint=true and no contradiction exists.

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?

Four tightly written sentences, each carrying necessary information: the core action, parent-folder behavior, location constraints, idempotency, and permission requirement. No filler or redundancy.

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 simple two-parameter tool with no output schema, the description plus annotations cover purpose, path semantics, permissions, idempotency, and safety. An agent has enough to invoke it correctly without missing critical context.

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 the schema already documents both parameters. The description adds value by explaining that the path creates missing parent folders and that dryRun performs no write, though much of the parameter semantics already lives in the schema.

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 specific verb and resource: 'Create a folder in Foundry's data storage', with additional scoping such as creating missing parent folders. This clearly distinguishes it from sibling operations like folder-rename and folder-delete.

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?

It provides clear usage context: creates missing parents, leaves existing folders untouched, and requires the write switch. Location restrictions are explicit ('Never inside modules, systems or another world'), though it does not explicitly name alternative tools for similar file operations.

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