set_light_2d_param

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

With no annotations provided, the description carries the full burden of disclosing behavior. It only says 'set a parameter' and omits side effects, required scene context, valid parameter values, or error behavior, which is insufficient for a mutation tool.

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 that immediately conveys the core function without wasted words. It is appropriately concise for a simple setter, even though this brevity sacrifices depth (penalized 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?

Given the tool has four unannotated string parameters, no enums, and no output schema, the description is not complete enough for correct invocation. It omits parameter semantics, valid values, and any behavioral context, making it insufficient for a non-trivial mutation 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?

Schema description coverage is 0%, and the description adds no meaning to the four generic string parameters. It does not explain what 'param' values are accepted, how 'value' should be formatted, or how to reference the light node, leaving the agent without necessary guidance.

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 the action ('Set') and the target resource ('2D light node'), with 'parameter' as the object. It also distinguishes itself from the sibling tool set_light_param by specifying '2D,' which helps the agent select the correct tool.

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 implies usage on a 2D light node but provides no explicit guidance on when to choose this tool over alternatives like set_light_param or read_light_2d. No exclusions or alternative recommendations are given, leaving the decision to the agent.

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