download_file

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the risk profile is partly covered. The description's prompt-injection warning is genuinely useful context beyond the annotations, but it never discloses the actual reason for destructiveHint: the tool writes to the local filesystem and can overwrite an existing output_path. Consistent with annotations, no contradiction.

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, front-loaded with the operation and then the safety note; each carries content. The injection warning is a bit boilerplate-heavy but is not padding for a tool that returns collaborator-authored text.

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?

With no output schema, the description should tell the agent what comes back (file content vs. a path) and where the file lands. It covers the security dimension well but leaves return shape and local-write/overwrite semantics to the schema and inference.

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 100%, so project_id, remote_path and output_path are all documented in the schema, giving baseline 3. The description only restates that the remote path is project-relative and adds nothing about output_path defaults or overwrite behavior.

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?

States a concrete verb and resource ('Download a single file from an Overleaf project') plus the addressing key ('by its path within the project'). It does not differentiate itself from siblings like download_pdf or pull_project, which handle overlapping needs.

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?

There is no guidance on when to choose this over download_pdf (single compiled PDF) or pull_project (whole-project sync), which are the obvious alternatives. The second sentence is a security caveat, not usage guidance, so the agent must infer selection criteria.

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