remove_background

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals the technique (DIS + Laplacian Matting) and the ability to preserve smoke/gradients. However, it does not discuss edge cases, such as performance on large images or potential artifacts, but overall it provides meaningful behavioral context.

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 extremely concise, consisting of two sentences that front-load the technique and purpose. Every word adds value, with no waste.

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 5 parameters and an output schema, the description is fairly complete. It explains the technique and expected quality (preserving smoke/gradients). However, it could briefly mention input image constraints (e.g., formats like PNG/JPG are implied but not explicit) or what the output is (e.g., image with transparent background). With output schema present, the return value may be documented, so this is not a major gap.

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 100%, so the schema already describes each parameter thoroughly. The description adds no additional meaning beyond the schema parameter descriptions; it only provides high-level context about the technique. Baseline 3 is appropriate.

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 uses advanced DIS and Laplacian Matting to extract backgrounds, specifying it preserves smoke, gradients, and soft artifacts. This is a specific verb-resource combination that distinguishes it from sibling tools, none of which perform background removal.

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?

While the description implies usage for background removal tasks, it does not explicitly state when to use this tool versus alternatives or when not to use it. There is no mention of prerequisites or limitations, which is a gap given the lack of annotations.

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