list_model_instance_versions

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

With no annotations provided, the description bears the full burden of behavioral disclosure. It only says 'List versions,' which implies a read operation, but it does not disclose pagination behavior, response contents, ordering, or whether it returns all metadata for each version.

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 clear, efficient sentence with no filler or repetition. It is front-loaded with the core purpose, though it is too terse to carry the behavioral and parameter context the tool needs.

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 has no annotations and no output schema, and the description is only one sentence. It does not explain what a returned version list looks like, how pagination works, what instance_ref values are valid, or how this relates to sibling operations. An agent would have to rely heavily on assumptions.

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 descriptions are 0% covered, so the description must compensate. It weakly maps 'for a model instance' to instance_ref, but gives no format or semantics for instance_ref and says nothing about page_size beyond what the schema already shows. This is insufficient given the lack of schema documentation.

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 a specific verb and resource: 'List versions for a model instance.' This distinguishes the tool from siblings like list_model_instances (lists instances, not versions) and list_model_version_files (lists files within a version), so an agent can tell them apart.

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 guidance on when to use this tool versus alternatives such as list_model_instances, list_model_version_files, or create_model_version. The description gives no exclusions, prerequisites, or context for choosing this tool over related siblings.

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