light_set_properties

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

No annotations are provided, and the description does not disclose behavioral traits such as side effects, error handling (e.g., if light node doesn't exist), or safety guarantees. The simple 'Set properties' implies mutation without elaboration.

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 structured with clear sections (Category, Args, Returns) and is reasonably concise. The 'Category' line adds context but could be omitted if redundant. Overall efficient for the parameter count.

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 has 9 parameters with dependencies on light type (e.g., 'range' only for PointLight3D/SpotLight3D), but this is only partially hinted in parameter names. Missing prerequisites (light must already exist) and behavior for invalid inputs. Output schema exists but description doesn't leverage it for completeness.

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 compensates by explaining each parameter's purpose (e.g., 'energy: Light energy/intensity', 'color: Light color as JSON array [r, g, b]'). However, units and constraints (e.g., valid ranges) are missing, leaving some ambiguity.

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 clearly states 'Set properties of a light source' with category 'Light', providing a specific verb-action and resource. It distinguishes from siblings like 'light_add' and 'light_set_shadow' by focusing on property modification.

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 explicit guidance on when to use this tool vs alternatives (e.g., 'light_set_shadow' for shadow-only changes). No prerequisites or exclusion criteria mentioned.

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