download_file

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

The description discloses the side effect of saving to a workspace directory and the differing return behavior (inline content vs. saved path). With no annotations provided, this transparency is valuable, though it does not mention potential errors or permissions.

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 redundant wording or fluff. Every sentence contributes useful information.

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 simple single-parameter tool, the description covers the essential aspects: what it does, where it saves, and how it returns results. It does not mention file size limits or error handling, but these are not critical for basic usage.

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?

The schema already provides a thorough description for the single parameter (including ID types and a query example), so the tool description adds little new meaning. Baseline of 3 is appropriate given high schema description coverage.

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) and resource (a file from Salesforce), and is distinct from all sibling tools which focus on records, SOQL, or analysis. It is immediately obvious when this tool is the right choice.

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 explains the ID types accepted and provides a query example to find them, which guides the user on how to obtain the necessary input. It also notes the behavioral difference between text and binary files, but does not explicitly contrast with alternatives (although no alternative download tool exists).

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