remove_background

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

With no annotations, the description carries the full burden, and it does disclose meaningful behavior: the mask is non-destructive ('the photo stays intact'), keep=background inverts the result, and backend=stability switches to an online service (implying a network dependency). It does not say whether an existing layer/project is required, whether the operation is undoable, or what happens to prior masks.

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?

Dense and front-loaded: the core outcome leads, then the inversion rule, then model and backend notes. Every sentence carries information, though the telegraphic style with '=' shorthand reads more like notes than prose.

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 5-parameter tool with no annotations and no output schema, the description covers the concept, model options and the online/local backend split, but leaves the required 'layer' and 'project' parameters and the post-call layer state unexplained. Adequate but with clear gaps.

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 0%, so the description must compensate, and it only covers three of five parameters (keep, model with concrete model names, backend). Required parameter 'layer' and 'project' receive no explanation, nor do the accepted values for keep beyond 'background'.

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 concrete outcome: an AI-driven cut-out rendered as a layer MASK while 'the photo stays intact', which an agent can distinguish from generic mask siblings like set_mask or update_mask. It doesn't explicitly name an alternative sibling, but the AI-cutout framing is specific enough to route correctly.

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?

Usage is implied rather than stated – there is no explicit 'use this when / not when' or named alternative among the mask tools. It does give selection guidance for two parameters (model choice, backend=stability for online processing), which partially compensates.

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