Remove the background of an image

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

Annotations indicate it is not read-only and not destructive. The description adds that the result is a new transparent PNG and returns { id, url, ... } for placement on a slide. It explains the non-destructive nature (creates new, doesn't modify original) but does not mention limitations like file size or processing time.

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 three sentences: action, input/output, and usage context. Every sentence adds value without redundancy, achieving high conciseness.

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 no output schema and moderate complexity, the description covers the main workflow, use case, and expected return format. It lacks mention of error conditions or edge cases (e.g., non-background images), but overall it is complete enough for typical use.

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 covers all three parameters with descriptions. The description adds context by specifying that the source attachment id comes from rootr_generate_image or an upload, and implies the nodeId is needed to attach the result to a presentation, enriching the schema's meaning.

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 verb 'Remove the background' applied to 'an existing Rootr workspace attachment', and specifies the output as 'a new transparent PNG'. This distinguishes it from sibling tools like rootr_generate_image that create images rather than process them.

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 provides context on when to use the tool: 'for product shots / logos / subjects that should sit on the slide without a boxed background.' It also mentions that the source attachment id comes from rootr_generate_image or an upload, but does not explicitly say when not to use or list alternatives.

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