light_create

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

The description discloses no behavior beyond a parameter hint, and the annotations provide only a title, not read-only or destructive hints. It does not say what happens when a light is created, whether it requires an active scene, or what side effects occur.

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 short, but brevity here reflects under-specification rather than conciseness. The single fragment adds minimal value and fails to earn its place as a usable tool description.

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?

With five unannotated parameters, no output schema, and no usage context, this description is far from complete. An agent would not know what the tool returns, what inputs mean, or how this creation operation differs from the many sibling light tools.

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, but it only documents light_type values. It gives no meaning for name, color, energy, or location, such as color format, energy units, or coordinate space.

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 is only 'light_type: POINT, SUN, SPOT, AREA.' It contains no verb or resource, so it never states that the tool creates a light. The purpose is only inferable from the tool name and annotation title, not from the description itself.

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 guidance on when to use this tool instead of sibling tools like light_set_params, light_setup_studio, or light_list. An agent cannot tell from the description which operation is appropriate for a given task.

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