set_light_properties

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses that the operation uses an inline Python LOP, which is useful, but it does not describe mutation side effects, safety implications, required prim state, error behavior, or return values.

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. It is efficient and easy to scan, though its brevity contributes to gaps captured in other dimensions.

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?

For a mutation tool with three required parameters, a nested object, no annotations, no output schema, and no schema descriptions, the definition is far too sparse. It identifies the resource and mechanism but omits parameter meaning, side effects, and operational context needed to invoke it confidently.

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 explain all three required parameters. It only implies that properties relates to light properties and prim_path to the light prim, while node_path is left unexplained and the properties object's expected keys and values are undocumented.

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 and resource: setting properties on a USD light prim. It also names the implementation mechanism, an inline Python LOP. It does not explicitly distinguish itself from generic siblings like set_usd_attribute, but the light-prim specificity is clear.

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 description defines what the tool does but gives no when-to-use guidance, no prerequisites, and no alternatives. It does not say whether the light prim must already exist, or when to use this instead of create_light or set_usd_attribute.

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