remove_background

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

With no annotations provided, the description carries the full burden. It details the underlying model (BiRefNet, state-of-the-art), capabilities (handles complex edges), endpoint stability, pricing (5 sats per image), and payment method (Bitcoin Lightning, no API key). This is highly transparent.

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 concise (5 sentences) and well-structured: first line states purpose, then technology, capabilities, then pricing and prerequisite. Every sentence adds value with no redundancy.

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 no output schema, the description adequately states the return type ('transparent PNG'). It covers payment flow, image formats, and model details. Minor omissions like size limits or timeouts do not detract significantly.

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?

The input schema covers both parameters with descriptions. The description adds context beyond the schema: it explains that paymentId requires a prior call to create_payment with toolName='remove_background', and imageBase64 supports data URI. This adds meaningful value.

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's purpose: 'Remove background from any image, returning transparent PNG.' It specifies the action (remove background) and resource (image), and is distinct from sibling tools like edit_image or colorize_image.

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?

The description provides clear context for usage, including the requirement to call create_payment beforehand. It does not explicitly state when not to use this tool or mention alternatives, but the context is sufficient.

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