blender_msfs_livery_transfer

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

With no annotations provided, the description carries the full behavioral burden but discloses only the UV-remapping mechanism. It fails to mention traits that are evident from the schema: the operation writes files to output_dir, consumes an external source_image, and likely requires aircraft template data — none of which an agent could anticipate as side effects or prerequisites.

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?

A single 10-word sentence with the core action front-loaded and zero filler. 'With UV remapping' earns its place by naming the operative mechanism, and every word contributes to conveying the tool's purpose.

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 tool with six parameters (four required), no annotations, and no output schema, the one-liner is under-specified: it never states that results are written to output_dir, whether the source image is treated as read-only, or whether the target aircraft must be prepared in the scene first. An agent can identify the tool but cannot predict its side effects or required setup.

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 each parameter is already documented and the baseline is 3. The description adds only marginal value by confirming that source_aircraft and target_aircraft refer to different aircraft types, but it contributes no format, constraint, or relationship details beyond what the schema already states.

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 verb ('Transfer'), a clear resource ('livery design'), and a distinctive scope ('between different aircraft types') that sets it apart from every sibling livery tool, none of which perform cross-aircraft transfer. The mechanism ('UV remapping') adds useful precision about what the operation entails, making the purpose unambiguous.

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 guidance is given about when to choose this tool over related siblings such as blender_msfs_livery_map_elements, blender_msfs_livery_export_textures, or blender_msfs_livery_create_paint_layers. The description states only what the tool does, with no conditions, prerequisites, or exclusions to help an agent decide when transfer is the appropriate step.

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