Create folder

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

Annotations already disclose that this is a write operation (readOnlyHint=false), has external side effects (openWorldHint=true), and is not idempotent (idempotentHint=false). The description adds no additional behavioral context, such as conflict behavior, permission requirements, or side effects like recursive folder creation.

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 a single, efficient sentence with no unnecessary words. It is front-loaded and avoids redundancy, making it optimally concise for a simple tool.

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 tool with two parameters, the description omits critical details about behavior on folder existence, the effect of autorename, whether parent folders are created recursively, and error conditions. With no output schema and minimal annotation detail, this bare description is insufficient for an agent to use the tool correctly without guessing.

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 path parameter is well-documented in the schema with an example, but the autorename parameter lacks any description in both the schema and the tool description. With schema coverage at 50%, the description fails to compensate for the undocumented autorename parameter, leaving its semantics unclear.

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 'Create a folder at the given path' uses a specific verb and resource, clearly distinguishing it from sibling tools like move, copy, delete, and upload. The focus on 'folder' differentiates it from file operations.

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 usage is implied by the tool's name and description, but there is no explicit guidance on when to use it versus alternatives (e.g., using upload for files). No exclusions or conditions are mentioned, making it a minimal viable guideline.

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