Background Removal

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, and idempotentHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: results are written to disk and their paths returned, and the Unlimited model is plan-gated. It does not mention upload behavior or credit cost (both only surfaced via schema params).

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?

Purpose is front-loaded in the first clause, followed by model availability, use cases, and output behavior. It is compact for a ten-parameter tool, though the colon-chained sentences are dense and the model/plan note sits awkwardly between purpose and use cases.

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?

With no output schema, the description correctly states what comes back (file paths on disk) and covers model plan constraints. It omits the upload/credit-charging mechanics, but those are represented by dedicated schema parameters (estimate_only, unlimited_bundle), so an agent has enough to call the tool correctly.

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 all ten parameters are already documented in the schema, which sets the baseline at 3. The description restates the model choice and plan gating but adds no syntax or format detail beyond what the schema provides.

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 and resource ('remove the background and replace it with solid white'), which is more precise than the bare name. The 'Best for' clause distinguishes it from removal siblings like td_watermark_removal and td_fabric_texture_removal by use case, though it never names an alternative tool explicitly.

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 'Best for' list gives concrete scenarios (isolating motifs, product shots, prepping for layering), which implies when to reach for this tool. However, there is no when-not guidance and no pointer to the sibling removal tools an agent should consider instead, so routing is left to inference.

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