list_ollama_models

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

No annotations are provided, so the description carries the full disclosure burden and discloses essentially nothing behavioral: no indication of whether results are local or remote, whether filters/pagination apply, or what an empty result means. For a simple read tool this is a modest gap, but the description adds no behavioral context at all.

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?

A single short phrase that front-loads the verb and resource with no filler. The parenthetical '(XPack)' is the only element that does not clearly earn its place, since it is not defined anywhere.

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 zero-parameter list tool with no output schema, the description is minimally adequate: an agent knows what it retrieves. It stops short of anything an agent would want for a list endpoint, such as what identifiers models carry or the shape/magnitude of the result set.

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?

The tool takes zero parameters, so per the baseline there is nothing for the description to disambiguate and the schema (empty object) is fully consistent. No parameter-level detail is needed or missing.

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 pairs a specific verb ('List') with a specific resource ('Ollama models'), which cleanly distinguishes it from the sibling mutation tools create_ollama_model, delete_ollama_model, and load_ollama_model. The '(XPack)' qualifier is unexplained, so an agent gets no help interpreting module scoping, but the core 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?

There is no statement of when to call this rather than sync_ollama_models, recreate_ollama_model, or close_ollama_model, and no preconditions or context are given. The listing verb implies read-only retrieval, but that is inferred rather than stated.

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