storage_download_file

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It only states the action without explaining whether this is a read-only operation, what the response format is (e.g., binary data, base64), or if any side effects occur. This is a minimal behavioral description.

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 a single, direct sentence with no wasted words. It is appropriately sized for a simple download operation and is front-loaded with the essential action.

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?

No output schema is present, so the description needs to explain what the tool returns. It fails to mention return type, encoding, or error behavior. For a download tool, this ambiguity could prevent an agent from using the result correctly.

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 clear descriptions for 'path' ('File path in bucket') and 'bucket' ('Bucket name'). The tool description itself adds no extra parameter semantics, so it meets the baseline of 3 for relying on schema.

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 'Download a file from storage' uses a specific verb ('Download') and resource ('file from storage'), clearly distinguishing it from sibling tools like storage_upload_file, storage_delete_file, and storage_get_public_url. It is immediately obvious what the tool does.

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 provides no guidance on when to use this tool versus alternatives. It does not mention that storage_get_public_url might be preferred for public URLs, or that storage_upload_file is for the opposite operation. There are no prerequisites or context cues.

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