remove_background

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 discloses that the tool builds a workflow, enqueues on local GPU, returns prompt_id immediately, and delivers the cutout asset_id in a completion notification. It also notes auto-downloading of the BiRefNet model and actionable error messages if dependencies are missing.

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 a single paragraph of five sentences, well-structured with purpose, workflow, prerequisites, dependencies, error handling, and return information. Every sentence adds value without redundancy.

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?

Despite lacking an output schema, the description fully explains return values (immediate prompt_id, later asset_id), prerequisites, dependencies, and error behavior. For a specific image processing tool with moderate complexity, the description is complete and self-contained.

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 minor context beyond the schema, such as clarifying that the image filename must be uploaded first, but otherwise the schema already describes the parameters sufficiently (e.g., default values, auto-download behavior).

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 'Remove an image's background, returning a transparent (RGBA) cutout' with a specific verb and resource. It distinguishes itself from siblings by calling itself the 'high-level entry point' and referencing prerequisites like upload_image and stage_output_as_input, which are separate sibling tools.

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 on when to use the tool (background removal) and prerequisites (upload source first or use stage_output_as_input). It also explains dependencies (ComfyUI-RMBG node) and error handling. However, it does not explicitly state when not to use this tool or mention direct alternatives, though no direct alternatives exist in sibling tools.

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