Nudge Key Light Elevation Down

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

The description discloses a behavioral trait (automatically queries fresh state before adjustment) that adds value beyond annotations (none provided). This helps the agent understand the tool's state-awareness. However, it does not mention error handling 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 with no wasted words. The purpose is front-loaded, and the behavioral note is efficiently placed. Every sentence adds value.

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's simplicity (one optional parameter, no output schema), the description covers the necessary context: what the tool does, its relative nature, and its state-querying behavior. It is mostly complete, though a brief note on when not to use (e.g., if degrees is too large) could enhance completeness.

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 coverage is 100% with a clear description for the 'degrees' parameter. The description itself adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate.

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 that the tool adjusts key light elevation downward relative to current position, using a specific verb ('Adjust'), resource ('key light'), and direction ('downward relative to current position'). It distinguishes itself from the sibling 'nudge_key_light_elevation_up' and absolute adjustment tools.

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 provides no guidance on when to use this tool versus alternatives, such as 'swing_key_light_down' or absolute set tools. It does not include prerequisites, when-not-to-use, or explicit context for selection.

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