remove_background

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

Without annotations, the description carries the burden of disclosing behavior. It explains the transformation (background removed) and the output format (transparent WebP), and notes the input is a local image. However, it does not mention side effects like overwriting, default output behavior when output_path is null, or error conditions, leaving some behavioral gaps.

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 a single sentence of 12 words, highly concise and front-loaded. Every word earns its place, clearly stating the action and result without 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 the tool's simplicity and the presence of an output schema, the description covers the core functionality. However, it omits important operational details such as default output path behavior and whether existing files are overwritten. It is minimally complete but lacks robustness for an unannotated tool.

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?

With 0% schema description coverage, the description should compensate. It clarifies that image_path refers to a local image, but it does not explain the output_path parameter at all, including its optionality or default behavior. The description adds minimal value over the raw schema.

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 function: removing the background from a local image and saving a transparent WebP. This specific verb+resource structure distinguishes it from the sibling tools, which are about candy prompt refinement and image generation, making the purpose 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 when the user wants to remove an image background, but does not explicitly state when to use it versus alternatives or mention any prerequisites. Since sibling tools are unrelated, the implied context is sufficient for basic selection, though explicit guidance is missing.

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