overleaf_create_project

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

There are no annotations, so the description must carry the behavioral burden. It discloses the operation, the 'empty' initial state, and the intended follow-up upload, but it does not mention authentication requirements, potential failure modes, or what the call returns. This is adequate for a simple create action but not rich.

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?

Two sentences with no wasted words. The core action is front-loaded, and the usage guidance and next-step reference earn their place.

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 one-parameter create tool with no output schema, the description covers what the tool does, when to use it, and the natural next step. The only notable gaps are authentication prerequisites and return value, which are minor given the low complexity.

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 100%, and the schema already documents project_name as 'Name for the new project.' The description adds workflow context but no additional formatting, constraints, or semantic detail for the parameter, so the baseline of 3 is appropriate.

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 action: 'Create a new empty Overleaf project.' The verb is specific, the resource is clear, and the word 'empty' distinguishes this tool from the sibling overleaf_create_project_from_zip.

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 says to use the tool 'when starting a paper from scratch' and explicitly names overleaf_upload_file as the next step. It does not explicitly mention when not to use it or contrast with overleaf_create_project_from_zip, but the 'empty' qualifier provides enough contextual direction.

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