Create a folder

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

The description merely restates that a folder is created and reveals nothing about side effects, idempotency, error behavior, or what happens if the folder already exists. Annotations provide no extra behavioral context beyond basic flags, so the description carries the burden and does not meet it.

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 filler or redundant modifiers. It is appropriately front-loaded, though it sacrifices semantic richness for brevity.

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 three-parameter create operation, the description combined with the schema is minimally viable: an agent can see the required projectId and name plus optional parentPath. However, with no output schema and no parameter descriptions, the description still falls short of fully supporting correct invocation in ambiguous cases.

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%, and the description does not explain projectId, name, or parentPath. With zero compensation for the missing schema documentation, an agent cannot infer the meaning or expected format of any parameter.

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 states a clear action ('Create a folder') and a resource ('inside an Overleaf project'), so its purpose is unmistakable. It distinguishes itself from the sibling tool create_project by targeting folders rather than projects, though it does not explicitly name that sibling.

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?

No guidance is given about when to use this tool versus alternatives such as write_file or upload_file. The phrase 'inside an Overleaf project' gives some context but does not state exclusions, prerequisites, or scenarios where a different tool is preferred.

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