Export project as ZIP

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

Annotations already cover read-only and idempotency. The description adds meaningful behavioral context: the output is written to outputPath on the local filesystem, and the archive contains the whole project. This goes beyond annotations, though it does not mention overwrite behavior or path prerequisites, which are minor gaps.

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, concise sentence with no filler. It front-loads the main action and resource, and every word contributes to understanding the tool's behavior.

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 two-parameter tool with no output schema and annotations covering idempotency and read-only behavior, the description is largely complete. It covers the core action and destination. It could clarify whether outputPath should be a file path or directory and whether existing files are overwritten, but these are minor gaps.

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 schema has zero descriptions, and the description compensates by referencing both parameters: projectId via 'whole Overleaf project' and outputPath explicitly as the write destination. It adds some meaning but does not specify expected path format, file naming, or any constraints, leaving room for ambiguity.

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 verb ('Download') and resource ('whole Overleaf project as a ZIP archive'), making it immediately clear what the tool does. This clearly distinguishes it from sibling tools like get_pdf, read_file, or compile_project, even without naming them explicitly.

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 implies when to use the tool (when you need the entire project as a ZIP) but gives no explicit guidance, alternatives, or exclusions. It does not mention when not to use it or point to any sibling for similar but different tasks.

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