Move Key Light Toward Direction

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

No annotations are provided, so the description must carry the full burden. It discloses that the tool automatically queries fresh state before adjusting, but does not mention whether the operation is destructive, reversible, or requires permissions. There is also no information about output or side effects.

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 two sentences long, front-loads the core action and key behavioral detail (auto-refresh), and lists directions concisely. Every sentence earns its place with no wasted words.

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 simple tool with only two parameters and no output schema, the description is fairly complete. It covers the action, behavioral trait, and parameter semantics. It could be improved by noting the coordinate system (relative to camera) and behavior for invalid directions, but overall it provides adequate context.

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 100%, so the schema already documents both parameters well. The description adds the default value for degrees (10°) and clarifies that movement is relative to current position, which is not in the schema. This adds some value beyond the structured data.

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 verb 'move', the resource 'key light', and the purpose 'toward a specific direction relative to current position'. It lists all available directions, distinguishing it from sibling tools like move_fill_light_toward_direction or nudge_key_light_elevation.

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 mentions automatic state refresh and lists directions, but lacks explicit guidance on when to use this tool versus alternatives like rotate_key_light_clockwise or swing_key_light_left. It does not specify when not to use it or provide exclusion criteria.

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