create_folder

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

With no annotations provided, the description bears full responsibility for disclosing behavior. It only states the action without explaining outcomes (e.g., success/failure), error handling, or side effects. Critical details such as whether it fails if the folder exists or if it creates intermediate directories are omitted.

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 exceptionally concise, using a single sentence plus a clearly labeled Args section. Every piece of text serves a purpose with no filler or repetition, 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?

This is a simple one-parameter tool, but the description lacks essential behavioral context such as error handling and whether intermediate directories are created. The presence of an output schema is noted, but without knowing its content, the description alone does not fully cover operational expectations. It is minimally viable but leaves gaps.

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 defines only 'path' as a string with no description. The description adds meaning by stating 'Full path for the new folder,' which clarifies that the path must be absolute rather than relative. This is valuable context for a single parameter, though it does not cover all possible constraints.

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 the tool's function: 'Create a new folder.' This is a specific verb and resource that unambiguously differentiates it from sibling tools, none of which create folders. No further clarification is needed.

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 provides no guidance on when to use this tool versus alternatives or any prerequisites or exclusions. While there are no direct siblings for folder creation, the description does not mention conditions like whether the folder already exists or if parent directories are required.

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