blender_msfs_create_emissive_material

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

With no annotations, the description carries the full burden, but it only states that a material gets created and does not disclose side effects such as whether the material is assigned to an object, what happens if material_name already exists, or how the day/night emission is implemented. The schema hints at behavior but the description does not confirm it.

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 zero redundancy. It states the action, target domain, and typical use cases in 11 words, so every word 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?

Together with a fully described schema, the description is workable for a simple material-creation call. It leaves gaps around prerequisites and side effects, and there is no output schema, so an agent still has to infer some behavior from the tool name and 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 description coverage is 100%, so the structured schema already documents all five parameters. The description adds no additional meaning to base_color, emissive_color, emissive_strength, is_day_night, or material_name; the baseline of 3 applies.

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 and resource: creating an emissive/light material for flight simulator. The parenthetical '(gauges, displays, lights)' plus the 'emissive' qualifier makes it distinguishable from sibling tools like blender_msfs_create_glass_material and blender_material_create.

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 parenthetical examples give clear usage context: gauges, displays, and lights are self-illuminated surfaces. It does not explicitly name alternatives or state when not to use it, but the context is strong enough for an agent to route to it.

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