Studio product photo

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

Annotations declare a non-read-only, non-destructive, closed-world write; the description adds real context beyond that: nothing is uploaded, it stays local, the source photo is presumably left intact, and background removal only happens when rembg is installed. It stops short of stating the returned value (e.g. the output path) or what happens on missing rembg.

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 core action is front-loaded in the first clause, and the closing 'Local only.' is an effective emphasis of the key constraint. The middle sentence is dense but every element (colour, shadow, scene, rembg) carries information.

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 six-parameter local file-writing tool with no output schema, the description covers inputs, side effects, and downstream consumption adequately. Missing only an explicit statement of the return value and default output-path behaviour, which the schema partially supplies.

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 83%, so the parameters are largely self-documenting; the description reinforces the background vs. scene distinction (brand colour backdrop vs. full scene photo) but adds no new semantics. The size range and keepBackground behaviour are left entirely to the 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?

States a concrete verb and resource: turn a seller's phone photo into a clean product shot, with the specific operations (colour/sharpness fix, background removal, studio backdrop, soft shadow). It also distinguishes itself from siblings by naming where the output goes (products[].image in content_kit or landing_page) rather than image sourcing (find_images).

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?

Gives a clear use context (prepping seller photos for content_kit or landing_page) and notes the local/no-upload condition. It does not state when-not to use it or contrast it with find_images for sourcing imagery, so the routing guidance is clear but not exhaustive.

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