Walk Key Light Out

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

Description discloses the basic behavior but no annotations exist. It does not mention any limits, side effects, or incremental nature of the movement. Adequate for a simple parameterless 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?

Single sentence, no filler. Front-loaded with verb and object, efficiently conveys the action and direction.

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 no parameters or output schema, the description sufficiently explains what the tool does. Lacks details on step size or continuity, but for a simple movement tool it is adequate.

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?

No parameters exist (schema coverage 100%), but the description adds meaning by explaining the spatial axis of movement, which is helpful for understanding the tool's effect without any schema details.

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 (move) and the resource (key light) with a specific direction (farther from center along axis). It distinguishes from the sibling 'walk_key_light_in' by implying outward movement.

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 guidelines on when to use this tool versus alternatives like 'walk_key_light_in' or 'dolly_camera'. No context on prerequisites or typical use cases.

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