create_folder

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

No annotations are provided, so the description carries the full burden. It discloses a key behavioral trait by noting "including intermediate directories," which informs the agent that parent folders will be automatically created. There is no mention of error handling, but for a simple creation tool this is meaningful transparency.

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 extremely concise: a single main sentence followed by a minimal Args section. It is front-loaded with the core purpose, and every sentence earns its place without any wasted words.

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 tool with one parameter and no output schema, the description covers the essential elements: purpose, parameter, and a key behavioral detail. It is not exhaustive but adequate for the tool's complexity; missing details like behavior when the folder already exists are not critical here.

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?

The schema provides only the parameter name and type (0% coverage). The description compensates by explaining that 'path' is the path to create and provides a concrete example ("/Documents/NewFolder"), giving the agent a clear sense of the expected format.

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 uses a specific verb ("Create") and resource ("folder"), and explicitly mentions "including intermediate directories," which clearly distinguishes it from other operations like copy, move, or upload. The purpose is unambiguous and directly tied to the tool's name.

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 description clearly states what the tool does, which implies when to use it (when a folder needs to be created). However, it does not provide explicit exclusions or mention alternatives among the sibling tools, so it falls short of a perfect 5.

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