list_model_version_files

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It correctly states a read-only 'list' action but does not disclose pagination behavior despite the page_size parameter, nor does it mention what file metadata is returned or whether output is sorted or recursive.

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 filler words or redundant restatement of the tool name. Every word contributes to the core purpose, making it appropriately concise.

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 tool with no annotations, no output schema, and 0% parameter schema coverage, the description is too thin for an agent to invoke confidently. It does not explain what version_ref should look like, how page_size affects results, or what the returned file list contains.

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%, so the description must compensate. It only hints that version_ref refers to a model instance version, but gives no format, identification details, or example. The page_size parameter is entirely unexplained beyond its default value 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 uses a specific verb ('List') and a specific resource ('files in a model instance version'), clearly stating what the tool does. It also distinguishes this tool from siblings like list_model_instance_versions (which lists versions, not their files) and download_model_version (which downloads rather than lists).

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 prefer this tool over alternatives such as download_model_version or list_dataset_files, and mentions no prerequisites or workflow context. The intended use is only implied by the tool name and one-line summary rather than explicitly stated.

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