download_model_version

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It does not mention that the tool writes files locally, where it writes them, whether untar defaults to false, or whether it creates directories/overwrites files. The word 'Download' implies a read operation, but important side effects on the local filesystem are undisclosed.

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 short sentence with no filler, so it is concise and front-loaded. However, it is under-specified: the sentence carries only the core purpose and provides no additional structure or context to help the agent use the tool correctly.

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 three undocumented parameters, no annotations, and no output schema, this one-sentence description is far from complete. An agent cannot determine the required input format, default behavior, output location, or return value. The definition is insufficient for reliable invocation.

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% and every parameter has an empty description. The tool description itself does not explain version_ref, output_dir, or untar. An agent has no way to learn that version_ref identifies the target version, output_dir sets the local destination, or untar controls archive extraction.

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 clear verb and resource: 'Download model instance version files.' This is enough to understand the basic operation and distinguish it from listing or creating model versions. It could be slightly more precise about which files and from which version, but overall the purpose is unambiguous.

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 gives no guidance on when to use this tool versus closely related siblings like list_model_version_files or download_dataset. There is no indication of prerequisites, when downloading is appropriate, or when an alternative would be better.

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