Download upload

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

Annotations declare readOnlyHint=true and destructiveHint=false, so the tool is clearly a safe read operation. The description adds minimal behavioral context: it says it downloads a file, but doesn't mention whether the file contents are returned as binary, whether it requires specific permissions, or if there are size limits. However, given that annotations already establish the safe read nature, the description's generic statement is acceptable but adds little beyond the annotations. No contradiction exists.

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 extremely concise—a single sentence with no filler. It's front-loaded with the action verb. However, it might be slightly under-specified, but conciseness alone isn't penalized; it's effective in being short. The structure is fine for a simple tool.

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 the tool has one parameter, a simple output (the file download), and annotations already cover the read-only nature, the description is almost sufficient. But for an agent in a toolchain with many download siblings, it lacks guidance on how this differs from downloading invoice attachments or credit notes. The description is complete for a standalone tool but not fully contextualized within the sibling set. Since there's no output schema, the description could mention that it returns the file content, but that's implied.

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 has one parameter, uploadId, which is 100% covered by the schema description 'Path parameter uploadId'. The description does not add any additional meaning (e.g., how to find the uploadId, what format it takes, whether it's a UUID or numeric). Since schema coverage is high (100%), the baseline is 3, and the description does not worsen or improve it. However, it could have added context like 'use the uploadId from bokio_list_uploads to download the original file', but it doesn't.

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 'Downloads an uploaded file' states a clear verb ('Downloads') and resource ('an uploaded file'), distinguishing it from operations like creating or updating. However, it lacks specificity about what type of uploaded file (e.g., does it correspond to an upload ID from a list endpoint?) and doesn't differentiate from sibling download tools like bokio_download_invoice_attachment, which download specific attachment types. The tool name is specific enough to hint at the upload context, but the description alone is somewhat generic.

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 implicitly suggests it should be used when the user wants to retrieve an uploaded file, but it provides no explicit guidance on when to use this tool versus alternatives like bokio_download_invoice_attachment or bokio_download_invoice. Given the list of siblings, an agent might struggle to know which download tool to select; the description doesn't clarify that this is for a generic upload (likely tied to an uploadId from bokio_list_uploads or bokio_get_upload) versus a specific attachment. This is a gap since the context signals show 40 sibling tools, and many are download variants.

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