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 well: it discloses the files.info resolution step, Bearer-token authentication, inline image downscaling, full-resolution disk saving, and the return path for non-image files. It stops short of covering overwrite behavior, error cases, or permission requirements.

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 purpose is front-loaded in the first sentence, followed by useful behavioral detail and then compact parameter documentation. Every section earns its place given the low schema coverage.

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 side-effectful download tool with no annotations, the description covers the important behavior: authentication, image handling, disk writes, and returned paths. An output schema exists, so return values need not be fully specified, but overwrite and error behavior remain unstated.

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 Args section adds needed meaning. It clarifies file_id with an example format and source, and explains workspace as a configured workspace name, though workspace could be more precise.

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 states a specific verb and resource: downloading a Slack file by its file ID. It is immediately distinguishable from sibling tools such as search_messages or read_channel, none of which download files.

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?

It explains that file_id is the Slack file ID found in message file metadata and that workspace is a configured workspace name. This gives clear usage context, though it does not explicitly discuss when not to use the tool or name alternatives.

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