Unload a specific LM Studio model instance by ID and verify it is no longer loaded. Use when freeing local resources, though active generations may be interrupted.
Unload precisely one instance and verify absence. May interrupt its active generations.
| Name | Required | Description | Default |
|---|---|---|---|
| instance_id | Yes |
Changes observed during successful MCP inspections.
v2.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare destructiveHint=true, and the description adds crucial extra context: it interrupts active generations and verifies absence afterward. This goes beyond the annotation by naming the side effect and the confirmation behavior.
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 short, front-loaded sentences with zero filler. Every clause adds new information.
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 one-parameter destructive tool with no output schema, the description covers the key risks (interrupting generations) and the verification step. Missing only explicit guidance on when to use it versus alternatives.
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?
Only one required string parameter (instance_id) with 0% schema description coverage. The description's 'precisely one instance' emphasizes that a single instance_id is expected and that multi-unload is not supported, adding useful constraint.
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?
States a specific verb (Unload) and resource (one instance), and specifies cardinality ('precisely one instance'). Does not differentiate from sibling lm_load, though they are natural opposites.
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 on when to use this versus lm_load or lm_load_advanced, and no preconditions stated. Usage is only weakly implied by the verb.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.