remove_background

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

With annotations covering the safety profile (destructive, idempotent, openWorld), the description still adds real operating context: an existing MEIGEN_API_TOKEN or saved local config is required on this legacy npm path, purchased credits are consumed, and local paths / public HTTPS URLs are uploaded automatically. It does not explain what happens to the credits on failure or the return shape, keeping it out of 5 territory.

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 first four sentences are tight and front-loaded, but the majority of the text is generic workflow boilerplate (budget planning, requestId persistence, recovery precedence, retry policy, caller-owned previews) that is not specific to background removal. For a two-parameter tool this is heavily over-specified and buries the useful content.

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 only two parameters at full schema coverage, no output schema and existing annotations, the description supplies what an agent actually needs: auth prerequisites, credit cost, upload behavior and the legacy-vs-OAuth endpoint distinction. Return-value details are appropriately omitted since there is no output schema to lean on, though the failure/charge behavior is thin.

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% and both parameters (requestId, productImage) are thoroughly documented in the schema, including accepted path/URL forms and retry semantics. The description only restates that one source photo is required and no prompt is needed, adding little beyond the schema, so the baseline 3 applies.

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?

"Create one transparent PNG cutout" names a specific verb, resource and output format, and the sentence "This removes the background; it does not create a new scene" separates it from the generative siblings (generate_image, generate_ai_background). No sibling is named explicitly, so it stops short of a 5, but the purpose is unambiguous.

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 gives some directional guidance ("for compositing, catalog assets or logos", "Use the dedicated skill directly; skip unrequested prompt enhancement, preference loading and delegation"), which implies when this tool is appropriate. However, it never states when to choose this over generate_ai_background or other transform siblings, so usage is only implied rather than explicit.

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