ollama_delete

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

No annotations exist, so the description must fully disclose behavior. It only states the action (delete) but omits critical traits: whether deletion requires the model to be stopped, whether it is reversible, error conditions, or permissions needed. This is a minimal and insufficient disclosure for a destructive operation.

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 zero redundant content. Every word contributes to conveying the tool's purpose.

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 simple delete operation with no output schema and no annotations, the description is insufficient. It lacks behavioral context (safety, prerequisites), meaning the agent cannot fully reason about the tool's usage. Information present in sibling tool names (e.g., ollama_status, ollama_list) could hint at preconditions, but the description itself is incomplete.

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 coverage is 100% and the single parameter 'model' already has a clear description 'Model name to delete'. The tool description adds no new semantic value; it simply restates the action. Baseline score of 3 is appropriate given the schema does the work.

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 'Delete an Ollama model' uses a specific verb (delete) and clearly identifies the resource (Ollama model). It is immediately distinct from sibling tools like ollama_list, ollama_run, or ollama_pull.

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?

No guidance is provided on when or when not to use this tool. There is no mention of prerequisites (e.g., model not be running), alternatives, or typical workflows. The agent receives zero context for decision-making.

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