remove_background

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

The description mentions returning a task id, status, and output URLs, but fails to disclose the asynchronous nature (with polling via wait parameter) and any rate limits, authentication, or potential costs. With no annotations, the description should cover more 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 with no waste, but it lacks structure such as sections or bullet points that could improve readability.

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?

With 5 parameters, no output schema, and no annotations, the description is too brief. It does not explain how to use the returned task id or the behavior of the wait parameter, leaving gaps for the agent.

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 only 40%; parameters like source_image_url, timeout_ms, and poll_interval_ms lack descriptions in both schema and tool description. The description does not add meaning beyond the schema's documented parameters (wait and model).

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 creates a Recraft task to remove background, which distinguishes it from sibling tools like upscale_image. However, it does not explicitly mention that the task is asynchronous.

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 like check_pricing or get_task. Usage is only implied through the tool name and sibling context.

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