download_file

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is well covered. The description adds the 50 MiB size cap and base64 encoding format, which are genuinely useful behavioral details beyond annotations. Does not disclose what happens on large files (error vs truncation), a minor gap.

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?

Single sentence, zero waste, front-loaded with the core action ('Read a file') followed by format and size limit. Every word earns its place.

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?

An output schema exists and the tool has one simple parameter. The 50 MiB limit and base64 format are the key constraints, both disclosed. With a read-only, idempotent tool and rich annotations, the description covers the operational essentials well. Could mention upload_file as the inverse counterpart for discoverability.

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 description coverage is 0%, so the description compensates minimally by naming 'base64' encoding and the 50 MiB limit. However, only one 'path' parameter exists, and its schema description ('Source path on the controlled computer') already conveys its meaning clearly. With a single well-described param, the description's marginal value is limited but adequate.

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 states 'Read a file from the controlled computer as base64' — specific verb (read/download) + resource (file) + direction (controlled computer) with size limit. It clearly complements the sibling upload_file. Could marginally improve by noting the file is transferred to the agent, but purpose is unambiguous.

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 gives no explicit when-to-use guidance or exclusion criteria. Context implies it pairs with upload_file (the inverse direction), but no alternative or caveat is mentioned. For a simple read tool, this is acceptable but not explicit.

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