set_light_param

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

There are no annotations, so the description must disclose behavioral traits. It only says 'Set light parameter,' which implies a mutation but does not explain what happens to the scene file, whether changes are applied to the editor or disk, if values are validated, or any side effects. This is insufficient for a mutation 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?

The description is a single concise sentence with no wasted words. However, it is overly terse and could benefit from including a bit more context while remaining concise. Good structure, but extreme brevity slightly reduces clarity.

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?

The tool is a mutation with 4 required parameters and no output schema or annotations. The description is minimal, lacking critical context like whether the modification affects the scene file directly, if a reload is needed, or how the value format is interpreted. Given the tool's complexity, this is incomplete.

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% with each parameter having a description, including examples for 'param'. The tool description itself adds no extra parameter meaning, so it relies on the schema. Baseline 3 is appropriate since the schema does the heavy lifting.

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 'Set light parameter' uses a specific verb and resource, but 'light' is ambiguous. It does not specify whether this is for a 3D Light3D node or a 2D Light2D node, and there is a sibling tool set_light_2d_param that implies this tool targets 3D lights. The purpose is clear in general but lacks explicit differentiation from related tools.

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 on when to use this tool versus alternatives like set_light_2d_param or set_shader_node_param. There is no mention of prerequisites, such as whether the scene must be open or the light must exist. The description gives no context for selection.

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