comfy_free_vram

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

Annotations already declare idempotentHint: true and destructiveHint: false, so the description doesn't need to repeat safety implications. The description does add detail on the two actions (unload models, free memory) which aligns with annotations (no contradiction). However, it doesn't discuss side effects like whether unloaded models need reloading, which could be relevant but is not critical for a safe, idempotent 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 exceptionally concise: a single purpose line followed by a two-line Args list. It is front-loaded with the main action, uses no filler, and every sentence adds value. Perfect structure for quick agent scanning.

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 two-boolean tool, the description fully explains what each argument does and the overall action. The existence of an output schema (not shown) likely covers return values. The only minor gap is that it doesn't mention any preconditions (e.g., whether models must be loaded) or post-conditions, but these are not essential for an idempotent cleanup operation.

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 schema provides only types and defaults (booleans with default 0), while the description adds meaning for each parameter: 'unload_models: Unload all loaded models from VRAM' and 'free_memory: Free cached memory allocations'. This clarifies what true values do, compensating for the 0% schema description coverage.

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 purpose: 'Unload models and/or free VRAM memory.' This is a specific verb-resource combination (unload models, free memory) that distinguishes it from sibling tools like comfy_check_vram (which checks) or comfy_emergency_stop (which stops execution). The title 'comfy_free_vram' reinforces the purpose.

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 (e.g., comfy_check_vram, comfy_restart, comfy_emergency_stop). It only states what the tool does, without context for selection or any exclusions. With 90+ sibling tools, this lack of decision support is a notable gap.

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