bokio_download_upload

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

With readOnlyHint=true and openWorldHint=true already declared, the description adds useful behavior by stating it writes to savePath and returns the written path and byte count. This is valuable because there is no output schema. It does not restate the schema's no-overwrite behavior, but the annotations already establish safety.

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 compact sentences with no redundant text. The main action and destination are front-loaded, followed by return behavior and sibling differentiation.

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 read-only download tool with fully described parameters and annotations covering safety, the description supplies the missing return-value context. It is complete enough for an agent to select and invoke the tool 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 description coverage is 100%, so uploadId, savePath, and companyId are already fully documented in the schema. The description mentions savePath implicitly as the destination but does not add syntax or meaning beyond the schema. Baseline 3 is appropriate.

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 an uploaded file's content to savePath. It also explicitly distinguishes the tool from bokio_get_upload by saying that sibling returns metadata. An agent can tell exactly what this tool does and how it differs from the metadata tool.

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 clearly indicates this tool is for retrieving file content and names bokio_get_upload as the metadata alternative. It does not explicitly cover when not to use it or mention other download siblings, but the primary usage decision is clear.

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