Download a Whatbox Path Locally

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

With no annotations providing safety or side-effect information, the description carries full burden and adds two concrete behavioral details: "Skips symlinks" and "checks local free space first." This goes beyond a generic download description, though it does not mention overwrite behavior or return values.

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 two concise sentences with no filler. The main purpose is stated first, followed by important caveats, making it easy to parse quickly.

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 tool with no output schema and zero parameter descriptions, the description provides the core purpose and two behavioral traits, but it omits parameter semantics and any guidance on expected results or failure conditions. This makes it minimally viable but not fully complete.

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 must explain the parameters. It mentions "remote file or directory" but does not clarify what "remoteRelativePath" is relative to, nor the meaning of "rootIndex." The agent cannot infer parameter semantics from the description.

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 clearly states the action ("Download"), the resource ("a remote file or directory"), and the destination ("configured local download directory"). This distinguishes it from sibling tools like whatbox_upload_path and whatbox_move_path.

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 the tool is for downloading remote content to local storage, but it does not explicitly mention when to use it over alternatives or provide any exclusions. The context of siblings makes the use case obvious, but there is no direct guidance.

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