unload_models

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

With zero annotations, the description carries the full disclosure burden and meets it well. It discloses scope ('all cached'), resource cost (100MB-400MB each), the non-destructive automatic reload behavior on the next background removal request, and the return shape. The auto-reload detail is exactly what an agent needs to assess the risk of calling this mutating utility.

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?

A front-loaded single-sentence summary is followed by brief, purposeful context on when to call, memory cost, and auto-reload behavior. The Returns line is slightly redundant given that an output schema exists, but the overall structure is tight and every other sentence earns its place.

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?

Complete for a zero-parameter utility tool with an output schema. An agent knows what the tool does, when to invoke it, why it matters (RAM relief), what it returns, and that it is safe because models reload automatically. Nothing needed to call it correctly is missing.

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 tool has zero parameters and 100% schema coverage, and the rubric establishes a baseline of 4 for zero-param tools. There is nothing to document and no coverage gap to compensate for.

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 opening line states a specific verb ('Unload'), a precise resource ('all cached ML models'), and the goal ('free memory'). The action is inherently distinguishable from siblings such as remove_background, list_background_models, and get_model_cache_status, all of which serve clearly different operations.

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?

Provides explicit timing guidance: 'Call this tool when you're done processing images to free up RAM.' It doesn't name sibling alternatives by name, but the trigger condition is unambiguous and clearly implies this is the cleanup counterpart to the image-processing flow, exceeding mere implied usage.

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