Download File

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

With no annotations, the description carries the full burden and does disclose real behavior: transfers route through Tor, writes land in TOR_DOWNLOAD_DIR, and existing files are never overwritten (an important, non-obvious safety trait). It omits auth needs, size/time limits, timeout behavior, and failure modes, keeping it short of a 5.

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 tight sentences with zero waste: destination and mechanism first, then the output_path semantics and overwrite policy. Every clause 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?

Covers both parameters, the destination, transport, and overwrite policy, which is solid for a 2-param tool. However, with no output schema and no annotations, the description should say what the call returns (e.g. the saved path) and any practical limits, which it does not.

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 both parameters are already documented, including that output_path is relative. The description largely restates that (relative to TOR_DOWNLOAD_DIR) and adds only the no-overwrite behavior; baseline 3 is appropriate when the schema does the heavy lifting.

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?

Names a specific verb (download), the resource types (document, image, archive, data file), the transport (through Tor), and the destination (TOR_DOWNLOAD_DIR). An agent can distinguish this from fetch_page, which retrieves page content rather than persisting a file.

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?

Usage is implied rather than stated: the mention of 'download directory' and 'through Tor' signals this is the file-persisting option versus fetch_page, but no explicit when-to-use, prerequisites, or alternative is named. Adequate but with a clear gap.

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