create_light_rig

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

Describes basic behavior (creates multiple lights, intensity, target) but lacks specifics on side effects, default placement, or behavior when target is invalid. No annotations to offset.

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?

Two concise sentences plus parameter list and return value description. Front-loaded, no redundancy, every sentence adds value.

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?

Covers key aspects: creation of multiple lights, intensity, targeting. Lacks details on precise rig layout or return schema, but adequate for a straightforward tool.

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?

With 0% schema description coverage, the description adds meaning by listing allowed values for type and explaining target and intensity. Could be more precise about 'point at' behavior.

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?

Clearly states it creates a pre-built lighting rig with multiple lights, distinguishing it from singular light creation tools like create_light. The description specifies common setups and lists types.

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?

Implies usage for standard lighting setups via the rig types, but does not explicitly state when or when not to use it, nor compare with alternatives like create_light or set_light_property.

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