overleaf_create_project

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

The description states only that a project is created, without detailing any behavioral traits such as side effects (e.g., does it overwrite existing projects?), authentication requirements, or rate limits. Since no annotations are provided, the description carries the full burden, and this minimal disclosure is insufficient.

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 one short sentence conveying the essential purpose with no extraneous words. It is front-loaded and efficiently communicates the core function.

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 that there is no output schema and the tool performs a creation action, the description is incomplete. It does not mention what the tool returns (e.g., project ID or URL), error conditions, or the scope of the blank project (e.g., default permissions). For a simple tool, this is a significant gap.

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 input schema covers the single parameter (projectName) with a description that already mentions the automatic prefix. The tool description adds no additional parameter-level meaning beyond what the schema provides. With 100% schema coverage, the baseline expectation is met.

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 specifies a concrete action ('Creates a new blank project') with a clear verb and resource. It distinguishes from sibling tools like overleaf_create_doc (which creates documents within a project) and overleaf_compile_and_download, leaving no ambiguity about its role.

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 explicit guidance is given on when to use this tool or when alternatives might be better. However, since no sibling tool creates projects, the usage context is implicitly clear (create a new top-level project). The lack of prerequisites or exclusions prevents a higher score.

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