system_ollama_models

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

No annotations are provided, so the description carries the burden. It discloses that the tool lists models with sizes and compatibility info, but does not explicitly state that it is read-only or describe any side effects, permissions, or failure behaviors. For a listing tool this is adequate but not rich.

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?

Two concise sentences, front-loaded with the primary action ('List all locally available Ollama models with their sizes'), and no wasted words. Every sentence contributes value.

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 is simple with no parameters and no output schema. The description covers the main return content (models, sizes, compatibility) and is sufficient for the agent to understand the tool's output. It could mention the format of the compatibility flags, but is otherwise complete.

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?

With zero parameters, the baseline is 4. The description adds meaning beyond the empty schema by specifying the output includes sizes and AION/Nebula compatibility, giving context to what the tool returns.

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 lists all locally available Ollama models with their sizes, and adds the specific purpose of showing compatibility with AION and Nebula. This is a specific verb-resource pairing that distinguishes it from query tools like ollama_query.

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 implication is to use this for checking model availability and AION/Nebula compatibility, but there is no explicit guidance on when to use this tool versus alternatives or any exclusion criteria. The utility is implied, not stated.

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