download_directory

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

With no annotations provided, the description carries the transparency burden. It discloses the internal process (compress, download, extract) and advises async for large directories, which goes beyond the schema. It doesn't discuss failure behavior or cleanup, but for a download tool this is reasonable.

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 sentences long, front-loaded with the purpose, and every word adds value. The parenthetical pipeline and async hint are concise and well-structured.

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 4-parameter tool with a full input schema, the description explains the operation pipeline and provides a performance tip. No output schema exists, but return values are not critical for a download operation. The description is adequately complete for choosing and invoking the tool.

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% with all parameters described. The description adds minimal extra parameter context, only reinforcing the async_transfer hint already present in the schema. Given the full schema coverage, the baseline of 3 is appropriate.

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 'Download remote directory' with a specific verb and resource, and the pipeline (remote compress → download → local extract) further clarifies the operation. It is distinct from sibling tools like download_file (file vs directory) and upload_directory (download vs upload).

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 clear context that this tool is for downloading directories and provides an explicit usage hint: 'Use async for large dirs'. It doesn't explicitly name alternatives, but the tool name and description make when-to-use clear enough.

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