clear_vram

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

No annotations are provided, so the description carries the full burden. It unambiguously states the action: unloading cached models frees GPU VRAM. It also discloses optional behavior: 'Optionally unload only models or only memory.' This is sufficient for a straightforward tool with no destructive side effects beyond clearing caches.

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 concise: two sentences without wasted words. The first sentence states the core purpose; the second adds usage guidance and parameter hints. Information is front-loaded and easy to parse.

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?

Given the tool's simplicity (2 boolean parameters, no required params, no output schema), the description covers all necessary aspects: purpose, usage scenarios, and parameter options. No additional information is needed for effective use.

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%, baseline 3. The description adds value by explaining the optional choices: 'Optionally unload only models or only memory.' This clarifies that the two boolean parameters can be used independently, enhancing understanding beyond the schema's individual descriptions.

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's function: 'Free GPU VRAM by unloading cached models from ComfyUI.' It specifies the verb (Free), resource (GPU VRAM), and context (ComfyUI). Among siblings, it uniquely addresses VRAM management, distinguishing it from other tools like model installation or generation.

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 explicitly advises when to use the tool: 'between generation runs with different model families (e.g. switching from SDXL to Flux) or when running low on VRAM.' While it does not explicitly state when not to use it or mention alternatives, the guidance is clear and helpful. A slight improvement would be to note that this is preferred over restarting ComfyUI for model switching.

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