remove_background

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

The description only discloses the size limit. It does not specify if the output is a transparent background, how the background_removal_task enum affects behavior, or any other side effects. Since no annotations exist, the description fails to adequately inform the agent about behavioral traits.

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 concise sentence that front-loads the core action. It could be expanded slightly without losing conciseness, but it is not verbose.

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?

The tool has 5 parameters including nested objects and an enum, but no output schema. The description does not explain what the tool returns (e.g., a new image with transparent background), nor does it cover constraints like image format or error handling.

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 the schema already documents all parameters. The description adds no extra meaning such as guidance on using the 'text' parameter or when to choose simple vs complex removal.

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 removes background from pixel art images with a maximum size constraint, making the purpose clear. However, it does not differentiate from sibling tools like inpaint or edit_image that could also manipulate backgrounds.

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?

No guidance is provided on when to use this tool versus alternatives such as inpaint or create_image_pixflux_background. The absence of usage context leaves the agent to guess.

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