aaddyy_background_remover

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

No annotations are provided, so the description carries the load. It adds useful behavioral detail: supported formats (PNG/JPG/WEBP), a 20MB size limit, the transparent PNG output, and a cost estimate (~2 credits). However it omits error handling, processing time, or what happens with unsupported inputs.

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 tight sentences, front-loaded with the core action, followed by constraints and cost. No wasted words.

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 simple single-param tool with no output schema and no annotations, the description covers purpose, constraints, output format, and cost. But the missing param semantics (how to pass the image) and error/edge-case handling leave it only adequate.

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 0% and the single 'image' parameter has an empty description. The description says to 'upload an image' but provides no format/encoding details (e.g., base64 vs URL) for the image param, leaving a real gap for a 1-param tool with no schema documentation.

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?

States a specific verb ('remove its background') and resource ('an image'), and explicitly distinguishes output ('clean transparent PNG cutout'). Clearly distinct from siblings like watermark_remover or upscale_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?

Implies usage by describing what it does, but gives no explicit when-to-use or when-not-to-use guidance and does not name alternatives. Adequate but no routing help.

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