Remove an image's background

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

With no annotations provided, the description carries the full burden, and it does disclose real behavior beyond the schema: the output is a transparent PNG foreground, results land in the output directory, and quoting a call generates nothing. It omits billing/cost behavior of the actual call, whether the source image is left untouched, and synchronous-vs-async semantics (though wait_s in the schema covers the latter).

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?

Two tightly packed sentences that are front-loaded with the action and result, then inputs, then side effects. Every clause earns its place, and the ideogram_quote pointer is a genuinely useful aside rather than filler.

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 6-parameter tool with no annotations and no output schema, the description covers purpose, output artifact, accepted inputs, and where results are saved. Missing only cost/permission expectations and an explicit statement that the operation does not alter the source image.

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 description coverage is 100%, so the baseline is 3. 'Takes a local file, a public https URL or an Ideogram asset' usefully maps to the image vs image_asset_identifier variants, but the description adds no detail on model, private, wait_s, or inline_images beyond what the schema already states.

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 states a specific verb and resource ('Remove the background of an image') and adds the concrete result ('the foreground comes back as a transparent PNG'), which an agent can immediately act on. It does not explicitly contrast itself with the sibling ideogram_replace_background, but the verb choice makes the distinction largely self-evident.

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?

It implies when the tool applies and enumerates the three acceptable input sources (local file, public https URL, Ideogram asset), and it points to ideogram_quote for pricing. It stops short of explicit when-to-use/when-not guidance or naming a competing sibling such as ideogram_replace_background or ideogram_precise_edit.

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