blender_msfs_livery_map_elements

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

No annotations are present, so the description carries the full burden of behavioral disclosure. 'Map' is ambiguous: it does not state whether this modifies the target, requires existing templates, or is a read-only lookup. The observable effects and return behavior are not disclosed.

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 a single, front-loaded sentence with no filler or redundancy. It delivers the core action and resource efficiently, making it easy for an agent to parse quickly.

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 annotations, no output schema, and an ambiguous core verb, the description is not self-sufficient. It lacks information about prerequisites, what 'mapping' changes, possible return values, and how this fits into the livery workflow among many related sibling tools.

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 coverage is 100%, but the description adds meaningful context by naming the valid design element types (cheatline, logo, registration), which clarifies the 'elements' parameter beyond its generic schema text. It also reinforces the relationship between source_aircraft and target_aircraft.

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 uses a specific verb and resource: 'Map design elements ... between aircraft templates,' and it lists concrete element types (cheatline, logo, registration). It clearly communicates the general operation, though it does not explicitly differentiate itself from sibling livery tools like blender_msfs_livery_transfer.

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 provided about when to use this tool versus related tools such as blender_msfs_livery_transfer or blender_msfs_livery_load_template_overlay. There are no stated prerequisites, exclusions, or workflow context, so an agent must infer the appropriate usage.

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