set_image_fill

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: WebP and other decodable inputs are normalized to PNG locally in the plugin. However, it doesn't state that the existing fill is replaced/overwritten or what happens on decode failure, so it stops short of rich behavioral disclosure.

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?

Two sentences, zero filler, and the primary action is front-loaded with the normalization caveat second. Every clause earns its place.

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 destructive, 4-parameter mutation with no output schema, the definition is adequate but thin: it leaves scaleMode, nodeId expectations, and failure/overwrite behavior unexplained, and there is no return-value note. The normalization disclosure is the one piece of real depth.

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 carries the full burden. It names the accepted image formats, which partially covers sourceMimeType, but says nothing about nodeId, scaleMode (FILL/FIT/CROP/TILE), or the 16 MB base64 cap. Three of four parameters remain semantically opaque.

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 ('Replace a node fill') plus the exact input form ('supplied as base64'), which implicitly distinguishes it from the sibling set_image_fill_from_path. An agent can tell what the tool does without opening the schema.

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?

No when-to-use, when-not-to-use, or alternative is given. The base64 wording hints at the split from set_image_fill_from_path, but the description never says to prefer the path variant when a file is on disk, leaving routing to inference.

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