start_ollama

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals the specific bind address, a queueing/approval behavior ('Extra calls wait for Late Approve'), and a limitation (no model pulls). It does not state what happens if Ollama is already running, but for a simple start command this is a solid disclosure.

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?

Three short sentences, each carrying distinct information: purpose and scope, concurrency behavior, and a key exclusion. There is no filler, repetition, or unnecessary detail, and the primary action is front-loaded.

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 no-parameter, no-output-schema tool with no annotations, the description covers the essential behavior, network scope, and a critical limitation. It does not mention how to confirm the startup result, but an agent could combine this with status/lifecycle siblings like ollama_status. This is nearly complete for the tool's complexity.

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 input schema has zero properties and 100% coverage, so there are no parameter semantics to document. The baseline for a no-parameter tool is 4, and the description appropriately focuses on behavior rather than parameters.

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 specific verb and resource: 'Start Ollama serve' on this computer, bound to 127.0.0.1:11434. This clearly distinguishes it from sibling tools like start_llamacpp and start_vllm by naming the exact service and scope. The 'Does not pull models' line further separates it from model-management siblings.

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 provides clear context by restricting the tool to a local 127.0.0.1:11434 startup and explicitly stating it does not pull models, which rules out using it for model acquisition. However, it does not directly name alternatives such as start_llamacpp or download_local_model, leaving some routing to inference.

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