create_light_rig

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

With no annotations, the description carries the full behavioral burden. It does not disclose what the rig actually creates (how many lights), whether it overwrites or adds to existing lights, whether it is undoable, or any required context. For a mutation tool with zero annotation coverage this is a real gap.

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 purpose is front-loaded in one sentence, and the args list is terse with no filler. The Args block is a reasonable structure, though it is somewhat list-like rather than prose.

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?

Parameters are well covered, but for a mutation tool with no annotations and no output schema, the description omits any indication of side effects, what is produced, or undo behavior. It covers the invocation surface but not the behavioral context an agent would want.

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 0%, so the description must compensate, and it does: it enumerates the valid preset strings ('three_point', 'studio', 'outdoor', 'hdri'), explains parent_path is a LOP network path, and clarifies intensity_mult scales all light intensities. This is meaningful added semantics for all three parameters, though the schema's 'preset' string has no enum to enforce these values.

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?

States a specific verb+resource: 'Create a preset lighting rig in a LOP network.' An agent can distinguish it from sibling create_light (single light) by the word 'rig' and 'preset'. It does not explicitly name or contrast against that sibling, keeping it just below a 5.

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?

There is no when-to-use guidance. The description never says when to prefer this over create_light or set_light_properties, nor any prerequisites (e.g. that a LOP network must exist at parent_path). Usage must be inferred from the name alone.

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