Remove bg

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

Annotations already flag destructiveHint=true, idempotentHint=false and openWorldHint=true, but the description adds real context beyond them: provider scopes/locks/credits consumption and a mandatory confirmation plus "one submission only" rule. That materially helps an agent understand cost and non-repeatability.

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 compact sentences, front-loaded with the endpoint and immediately followed by the highest-value operational constraints. No filler, though the leading endpoint token is low-information relative to the rest.

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 no output schema and a nested payload object, the description covers operational preconditions but says nothing about the actual result (e.g., a processed image reference) or which provider performs the work. Annotations carry the safety profile, making this adequate but not complete.

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 all four parameters (account, confirm, payload, payload_file) are already documented in the schema. The description adds no syntax or format detail about them, 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?

The description opens with "POST /v5/tools/remove_bg," which is effectively a restatement of the tool name and title rather than a description of what the tool does. It never states in prose that it removes the background from an image, nor distinguishes it from the many other media-processing siblings.

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?

There is no when-to-use or when-not-to-use guidance, and no alternatives are named despite many adjacent tools (generate_ai_image, apply_color_filter, etc.). The only usage-ish instruction is the confirmation requirement, which is a precondition rather than selection guidance.

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