Download a file

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the basic save-to-local-path action but does not mention whether existing local files are overwritten, whether directories are created, what happens if the source file is missing, or any permission requirements. This is similar to the update_drive example where mutation details were omitted.

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 that front-loads the core action and resource. It is appropriately brief, though it omits useful details that could be added without much verbosity.

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 three parameters, no annotations, no output schema, and many sibling tools, the description is too thin. It fails to explain projectId, distinguish from download_pdf, or clarify return/error behavior, leaving the agent with insufficient context for reliable invocation.

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 coverage is 0% and no parameter descriptions are present. The description partially compensates by mapping 'project file' to filePath and 'local path' to destPath, but it does not clarify the optional projectId parameter or its role in selecting the project. Two of three parameters are only implicitly described.

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?

Description clearly identifies the action ('Save... to a local path') and the resource ('any project file'), with explicit examples (PDFs, images) that distinguish it from the sibling tool overleaf_download_pdf. The verb 'save' effectively conveys 'download' without ambiguity.

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 provided about when to use this tool versus alternatives like read_file, read_image, or download_pdf. The phrase 'any project file' implies broad applicability but does not state exclusions or recommend when a different sibling would be more appropriate.

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