Swing Key Light Down

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

Describes the motion as rotating in an arc around the center, which provides some behavioral insight. However, with no annotations, it does not mention whether the rotation is incremental or continuous, or any limits.

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 that efficiently conveys the tool's purpose without extraneous details. Front-loaded and elegantly concise.

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 zero parameters and no output schema, the description adequately explains the tool's function. It could benefit from mentioning that this rotates the key light around the model center, but it's already implied.

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; the description adds no parameter information but is not required to. Baseline 4 applies for tools with zero parameters.

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?

Clearly states the action (rotate) and resource (key light downward) with specific detail about the arc around the center. Distinct from siblings like swing_key_light_up or swing_key_light_left.

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 guidance on when to use this tool versus alternatives like move_key_light_toward_direction or other swing directions. The agent must infer based on direction alone.

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