remove_model

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

With no annotations, the description carries the full burden. It discloses that the tool resolves paths across all configured roots, rejects path traversal/absolute escapes, and is local-only. This provides solid behavioral insight beyond a simple 'delete' statement.

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 mostly efficient, conveying key points in a few sentences. It could be slightly tightened (e.g., the parenthetical about extra roots is a bit dense), but it's still well-structured and front-loaded with the core action.

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 (one parameter, no output schema), the description is complete. It covers the action, path resolution, security restrictions, and local-only constraint. The agent has sufficient information to use the tool correctly.

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%, so baseline is 3. The description adds context beyond the schema: it explains how the path is resolved across multiple roots and that the leading segment is the category. This extra meaning helps the agent understand path construction.

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 it deletes a model file from local ComfyUI models directories, specifying it resolves across all configured roots. This distinguishes it from siblings like remove_extra_path (which removes a path entry) and download_model (downloads).

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 clear context for when to use (delete a model file) and explicitly states it's local-only (not for remote ComfyUI). It also explains path resolution across multiple roots. However, it does not explicitly list alternative tools for remote deletion.

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