create_folder

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

The description discloses that calling it on an existing folder returns a message, which is useful. However, it does not mention permissions, side effects, or error conditions beyond duplicate, leaving gaps for a tool with no annotations.

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 two sentences with no unnecessary words, front-loading the main purpose and then adding the duplicate behavior, making it highly efficient.

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?

Given the tool's simplicity (one parameter, no output schema), the description covers the success case and a key edge case (duplicate). It lacks details on error handling or return structure but is nearly complete for basic use.

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 description adds only 'with the given name' to the folder parameter, which is vague. It does not explain path format, relative vs absolute, or allowed characters, failing to compensate for the 0% schema description coverage.

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 verb 'create' and resource 'folder' with a specific behavior of returning a message if it already exists, distinguishing it from sibling tools like delete_folder.

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 implicitly states to use it for creating folders, but provides no guidance on when not to use it or alternatives. It mentions behavior on duplicate but lacks context compared to other tools.

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