Download file

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered structurally. The description's 'Read operation' merely echoes readOnlyHint and adds no new context such as auth/credential requirements or the meaning of the private output directory behavior. No contradiction, but essentially zero added value.

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 text is short but not concise in a useful sense: it is under-specified rather than economical, spending its two lines on a restated name and a redundant 'Read operation' while omitting everything an agent would need.

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 9-parameter tool with a nested payload object, a required output_file, private-credential 'account' semantics, and no output schema, the description is far too thin. It leaves the agent to reconstruct usage entirely from the schema and annotations.

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 the schema itself documents all 9 parameters including the required output_file and the nested payload object. The description contributes no parameter meaning, which is acceptable only because the schema does the heavy lifting; baseline 3 applies.

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 is essentially a tautology: it restates the tool name and title ('Download file') with no verb+resource elaboration, no scope, and no differentiation from the many sibling download tools (download_files, download_artifact_file, download_skill_file). An agent cannot tell what resource space this operates in from the text alone.

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?

There is no when-to-use, when-not-to-use, or alternative guidance whatsoever. With siblings like download_files, download_artifact_file, and download_skill_file in the toolset, the absence of any routing signal is a serious omission.

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