move_download_file

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

The description adds no behavioral detail beyond the annotations. It does not state whether server-side files are modified, whether local files are overwritten by default, whether authentication is required, or any side effects. The annotations declare idempotentHint and destructiveHint, but the description itself contributes little behavioral transparency.

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, front-loaded sentence with no wasted words. It is appropriately concise, though it sacrifices useful detail.

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?

The tool is simple, but the description leaves important gaps: no usage guidance versus move_download_job_outputs, no parameter semantics for two of three parameters, and no behavior around overwrite or local file handling. The output schema exists, so return values are not required, but the remaining ambiguity is significant.

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 only 33%, and the description does not compensate. file_id and overwrite have no descriptions in the schema and are not explained in the tool description. Only dest_path is clarified, and that is already done in the 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 clearly states the action ('Download'), the object ('a Move file'), and the destination ('to this machine'). It is specific enough to distinguish from upload and create tools, though it does not explicitly differentiate among related download/get siblings such as move_download_job_outputs.

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?

No guidance is given on when to use this tool versus alternatives. The phrase 'typically a job output' creates ambiguity because a dedicated move_download_job_outputs sibling exists, but the description does not say when to choose one over the other.

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