recraft_texture_swap

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

With no annotations provided, the description carries the burden, and it does disclose an informative behavioral workflow: generate new content, match aspect ratio, resize, and composite onto the original. It does not address credit consumption, original-file preservation, or failure modes, but the core nondestructive-ish output-to-output_path behavior is reasonably conveyed.

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 two focused sentences with no filler. The first sentence states the core action, and the second adds behavioral detail plus a concrete use case, all front-loaded and scannable.

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 9 parameters, a nested region object, no annotations, and no output schema, the description explains the main workflow and target use case but omits return behavior, prerequisite conditions, and how options like style or negative_prompt interact. It is adequate for selection but not fully complete for a complex tool.

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 the schema already documents all parameters in detail, including region, feather, model, and output_path. The description adds only high-level context about region compositing, not parameter-level semantics beyond the schema, matching the baseline for fully covered schemas.

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 specific verb and resource: replacing a specific image region with AI-generated content for texture swaps. It also clarifies the distinctive behavior—matching region aspect ratio, resizing, and compositing—which separates it from sibling tools like recraft_inpaint or recraft_erase_region.

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 explicitly frames the tool as 'Perfect for Spine atlas texture swaps and spritesheet updates,' giving a clear use context. It does not name alternatives or exclusions, so it stops short of full routing guidance, but the intended scenario is clear.

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