get_download

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

No annotations exist, so the description carries full burden. It clearly explains that images are returned as viewable images, and for non-images, behavior depends on includeContent (metadata only vs base64 inline, max 256KB). It does not address error cases, rate limits, or authentication, but the behavior is well-specified.

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?

Two sentences, front-loaded with the core action. Every sentence adds value: stating purpose, clarifying image behavior, and providing a recommendation. No wasted words.

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?

Given no output schema, the description adequately explains return values: images are viewable, non-images either base64 inline (if includeContent true) or metadata only with contentUrl. It does not cover error conditions or specific file type handling, but for a simple retrieval tool, it is sufficient.

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%, so baseline is 3. The description adds meaningful context for includeContent by explaining its effect (base64 inline for non-images, max 256KB) and the default behavior. For downloadId and userId, the description adds no additional meaning beyond the schema, but the includeContent guidance elevates the score.

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 'Get a downloaded file' with specific verb and resource. It distinguishes from siblings like list_downloads and delete_download by focusing on retrieval. The additional detail about images being viewable and guidance for AI agents further clarifies the tool's purpose.

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 recommends setting includeContent=true for non-image file content, providing explicit guidance on when to use that parameter. However, it does not discuss when to use this tool versus alternatives like list_downloads or delete_download, nor does it indicate when not to use it.

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