delete_model

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

No annotations are provided, so the description carries the full burden. The description only says 'Delete a model from Ollama,' which implies destructiveness but does not disclose that deletion is irreversible, whether it fails if the model is loaded, or any other behavioral traits. This is a significant gap 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 sentence with no extraneous words. It is front-loaded with the key verb 'Delete' and clearly identifies the resource. This is appropriately concise and well-structured.

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 one well-documented parameter and no output schema. The description is minimal but adequate for a basic delete operation. However, the lack of behavioral warnings (e.g., permanence, side effects) makes it slightly incomplete for an agent that should anticipate consequences, hence a score of 3.

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 fully describes the 'model' parameter with 100% coverage, so the baseline is 3. The description adds no additional meaning beyond what the schema already provides, as it simply repeats the name of the parameter without further elaboration.

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 a model from Ollama' clearly states the specific action (delete) and resource (model), making it distinct from sibling tools like list_models, get_model_info, or pull_model. This satisfies the requirement of a specific verb+resource with clear differentiation.

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 no guidance on when to use this tool versus alternatives, nor any prerequisites or conditions (e.g., model must not be in use, operation is permanent). It simply states what the tool does, leaving the agent without context on appropriate usage.

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