remove_background

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

With no annotations, the description must carry behavioral disclosure. It does mention the output format (transparent PNG) and a key requirement (matching provider key). However, it omits where the output is saved, whether the original is modified, and error behavior. This is partial but not comprehensive.

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 concise sentences. The main action and output are front-loaded, and the provider key note is placed second. No filler or redundant information. It earns its place efficiently.

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?

The tool has no output schema and no annotations, so the description must explain what happens on success and failure. It only states the output is a transparent PNG but does not specify the output path, return value, or error conditions. For a transformation tool that produces a file, this is a significant 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?

The input schema has 100% description coverage, so all parameters are already documented. The description adds context about the provider key requirement, which clarifies the dependency between provider and key. This is a slight addition beyond the schema, so the 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 states a specific verb ('Remove') and resource ('background from an image'), and explicitly names the output ('transparent PNG'). This clearly distinguishes it from the sibling 'replace_background', which replaces rather than removes. The action and result are unambiguous.

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 implies usage: if you need to remove a background, this is the tool. However, it does not explicitly mention alternatives or when NOT to use it (e.g., for replacing a background, use replace_background). It only notes a prerequisite (provider key) but gives no comparative guidance.

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