move_get_file

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

Annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds valuable behavioral context by explaining that input files receive a PUT upload URL and job output files receive a time-limited download URL, which goes beyond the annotation hints.

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 very concise, front-loads the main purpose in the first sentence, and adds only the necessary distinction between input and output file URL behavior. Every sentence earns its place.

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 single required parameter, the readOnly annotation, and the presence of an output schema, the description covers the key nuance about presigned URL types. It could be slightly more complete by mentioning expiration or explicitly pointing to upload/download siblings, but overall it is sufficient for correct usage in most contexts.

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 0%, but the description adds no specific meaning for the file_id parameter. Although file_id is self-explanatory, the description does not compensate for the low coverage, nor does it clarify how the ID is used or where it comes from.

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 tool fetches a file and returns a fresh presigned URL, which distinguishes it from a direct content download. However, it does not explicitly name or contrast sibling tools like move_download_file or move_upload_file, so the differentiation is functional but not explicit.

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 explains the behavior of the presigned URL for input files versus job output files, implying this tool is for obtaining a presigned URL rather than transferring content directly. It does not explicitly state when to use this tool instead of move_download_file or move_upload_file, leaving the choice somewhat inferred.

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