remove_background

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

Annotations already declare the safety profile (destructiveHint=false, openWorldHint=true, idempotentHint=false), and the description adds that the result is a transparent PNG cutout. It does not disclose that a file is written to disk, whether an existing file at output_path is overwritten, or why the operation is non-idempotent — context the agent would need before running it on a real path.

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?

A single front-loaded sentence that names the action and the exact output format with no filler. Nothing is redundant or buried.

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?

An output schema exists, so return values need not be explained, and the description correctly covers the transformation and its artifact. The only real gap is routing versus the mask/background-altering siblings, which matters given six adjacent tools.

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 description coverage is 100%, so image_path, output_path and the model enum are already documented in the schema. The description contributes nothing extra about model selection trade-offs or format constraints, so the baseline 3 applies.

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) and resource (background) plus the concrete output artifact: a transparent PNG cutout of the subject. This is clearer than a bare 'remove background', but it never addresses the closest sibling, create_mask, which an agent could reasonably confuse with a subject-cutout operation.

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?

There is no when-to-use or when-not-to-use guidance, and no alternative is named. With six siblings including create_mask, blur_background, color_background, gradient_background and add_shadow, the agent is left to infer that this tool is the one that isolates the subject rather than altering the background.

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