overleaf_create_project_from_zip

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

With no annotations provided, the description carries the behavioral disclosure burden. It does disclose an important safety behavior: it never overwrites an existing project. However, it omits other relevant behaviors such as authentication requirements, handling of invalid ZIP files, or whether duplicate projects may be created.

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 filler. The core action is front-loaded, and the important non-overwrite guarantee is included without unnecessary detail.

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 relatively simple creation tool with fully documented parameters, the description provides the key usage cue and a critical safety guarantee. It is slightly light on expected outcomes or failure modes, but nothing essential for invoking the tool correctly appears to be missing.

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 has 100% description coverage for both zip_path and project_name, so the structured schema already documents the parameters well. The description adds little beyond the schema, but the baseline of 3 applies because no additional parameter semantics are needed.

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 specific action and resource: creating a new Overleaf project from a local ZIP archive. It also differentiates itself from sibling tools like overleaf_create_project by emphasizing the ZIP source and the non-overwrite behavior.

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?

It explicitly says to use this tool for importing a complete existing paper and clarifies that it creates a separate project, which gives clear context for when it is appropriate. It does not explicitly name alternatives or exclusions, but the use case is clear enough for an agent to route correctly.

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