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

Beyond the annotations (readOnly=false, destructive=false, openWorld=true), the description discloses the credit cost (0.5, or 1 over 25 megapixels) and the async behavior: a job_id may be returned, in which case the agent must poll pigmenta_job_status and not re-invoke. That is exactly the operational context annotations cannot carry. It does not describe the output artifact itself, but the safety/mutation profile is consistent with the annotations.

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 and its mode selection are front-loaded, followed by cost and async handling, which is a sensible order. The prose is dense and slightly run-on, but nearly every clause carries operational information rather than filler.

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 and 0% schema description coverage across six parameters, the description should do more than it does: the input source (image vs image_url vs handle) is never clarified, nor is what the tool returns. It does cover the async path and cost, which are the hardest parts, so it is adequate but incomplete.

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 0%, so the description must compensate, and it only partly does: it explains 'remove' values, the color_hex dependency, and that tolerance is a 0-255 pixel-proximity threshold. Three of six parameters (image, handle, image_url) receive no explanation at all, leaving a meaningful gap.

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 names a specific transformation (making black, white, or one chosen color transparent) and frames the use case (knockout for DTF on dark or light garments). An agent can distinguish this from a generic background remover, though it never explicitly contrasts itself with the sibling remove_background tool.

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?

It gives useful selection rules among its own modes ('black' default, 'white', or 'color' with color_hex required), which is real when-to-use guidance. However, it offers no guidance on when to prefer this over remove_background or the other image siblings, leaving the cross-tool decision to inference.

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