blender_msfs_livery_load_template_overlay

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

No annotations are provided, so the description must disclose behavioral impact. It only states the intended effect without explaining whether the overlay replaces existing overlays, requires paint mode setup, or modifies the Blender scene state. This is a significant transparency gap for a state-changing tool.

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 front-loaded sentence with no filler. It conveys the core action efficiently and earns its place without redundant wording.

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?

Without annotations or an output schema, the one-line description leaves out workflow context that an agent would need, such as whether this should follow template download, whether paint mode is required, and what visual/state change occurs. It is minimally understandable but not fully complete for correct use.

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 baseline is 3. The description adds little beyond 'template image', which loosely maps to image_path, but opacity and object_name semantics are only documented in the schema.

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 ('Load'), a clear resource ('reference template image'), and the intended purpose ('as overlay for painting'). It does not explicitly differentiate from the sibling blender_reference_image_setup, but the MSFS livery context and 'template' wording clarify the domain.

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 phrase 'for painting' implies use during a livery painting workflow, which gives some usage context. However, it does not mention alternatives, prerequisites, or when not to use this tool, especially compared to related tools like download_template or reference_image_setup.

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