create_folder

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the description's idempotency claim largely restates structured data. It does add genuine context beyond the annotations by explaining that parent directories are created automatically by default and what 'idempotent' concretely means (creating an existing folder succeeds). It stops short of covering permissions or error behavior.

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 short sentences, front-loaded with the core action and followed by the two most decision-relevant behaviors. No filler or repetition.

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?

An output schema exists, so return values need not be described, and annotations carry the safety profile. Still, with 0% schema coverage the description leaves force_parent's non-default behavior and the expected path format unstated, which is thin for a mutating tool that accepts an array of paths.

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 0% for two parameters. The description hints at the paths array via 'one or more new folders' and alludes to force_parent's default via 'automatically by default', but it never names force_parent or explains what happens when it is set to false, so the override semantics remain undocumented.

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 ('Create ... new folders') and adds batch scope ('one or more'). It is clear on its own, but does not explicitly distinguish itself from adjacent siblings such as upload_file or copy_files that also produce new directory entries.

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?

There is no when-to-use / when-not-to-use guidance and no named alternative. The agent must infer from the name alone that this is the tool for creating directories rather than uploading or copying content into them.

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